Hi,
On Wed, 2007-01-10 at 21:43 +, Meetesh Karia wrote:
PostgreSQL version: 8.0.10
Operating system: Centos-4.2
Description:RPM: wrong quoting of error message about old database
format after upgrading
I changed that message for PGDG 8.0 RPMs. The other releases do not have
Ravi Periasamy wrote:
I do not think this is a server issue, seems like a
driver issue. When I connect to the DB from RHEL4
through the driver (running on RHEL4) it works. But,
when the driver is running on RHEL3 it fails.
Oh, I hadn't realized that both clients were connecting to the same
I do not think this is a server issue, seems like a
driver issue. When I connect to the DB from RHEL4
through the driver (running on RHEL4) it works. But,
when the driver is running on RHEL3 it fails.
Anyways, here's the output:
[EMAIL PROTECTED] pgsql]# pg_controldata `pwd`/data
pg_control
A after thought- I was working with Oliver Cloud on a
similar issue and he has a fix for that issue, that
would solve this as well.
Basically the changeTime() method called from
Statement.getDate(int, Calendar) is causing the
problem. Make sure, the code from
ResultSet.getDate(int, Calendar) is
The following bug has been logged online:
Bug reference: 2885
Logged by: Akio Iwaasa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Redhat EL ES 3.0
Description:to_char function
Details:
When I've used to_char function to convert Date
select version();
PostgreSQL 8.2.1 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.4.2 (mingw-special)
pg_log:
2007-01-12 16:41:23 STATEMENT: EXPLAIN COPY MsgRoot TO 'C:/Program
Files/PostgreSQL/8.2/data/MsgRoot.txt'
2007-01-12 17:16:04 LOG: checkpoints are occurring too frequently
Akio Iwaasa [EMAIL PROTECTED] writes:
When I've used to_char function to convert Date to
century format text, '2000-01-01' was converted in
the 21st century.
postgres=# select to_char('2000-01-01'::date, 'CC') ;
to_char
-
21
(1 row)
I'm not entirely sure that this is
I updated our documentation for CC:
entrycentury component of year (minimum 2 digits)/entry
---
Tom Lane wrote:
Akio Iwaasa [EMAIL PROTECTED] writes:
When I've used to_char function to convert Date to
Bruce Momjian [EMAIL PROTECTED] writes:
I updated our documentation for CC:
entrycentury component of year (minimum 2 digits)/entry
Updating the documentation isn't a solution; either the code is correct
or it's not, and I rather suspect it's not (it's incompatible with
EXTRACT(CENTURY)
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the OLAP option
JServer Release 9.2.0.4.0 - Production
select ordh_dtinral, to_char(ordh_dtinral,'CC YY') from ordheader
where ordh_dtinral between '01-Jan-2000' and '01-Mar-2000';
ORDH_DTIN TO_CH
-
PostgreSQL 8.1.5 and 8.2.1
both on W2K3, installed from the standard win32 msi installer.
Problem:
in postgresql.conf
ssl=on
but the files server.key etc. are NOT present.
Result: PostgreSQL service does not start. And no error message in any
log I could access: nothing in the Windows Event
Douglas Toltzman [EMAIL PROTECTED] writes:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the OLAP option
JServer Release 9.2.0.4.0 - Production
select ordh_dtinral, to_char(ordh_dtinral,'CC YY') from ordheader
where ordh_dtinral between '01-Jan-2000' and
Akio Iwaasa [EMAIL PROTECTED] writes:
When I've used to_char function to convert Date to
century format text, '2000-01-01' was converted in
the 21st century.
I've patched this in HEAD and 8.2 branch.
regards, tom lane
---(end of
13 matches
Mail list logo
