Re: [BUGS] abstime bug

Michael Fuhr <[EMAIL PROTECTED]> writes: > SET TimeZone TO 'Asia/Hong_Kong'; > SELECT '1901/12/14 1:00'::abstime; > abstime > > 2038-01-19 07:51:40+08 > (1 row) > I'd guess this is due to the 32-bitness of abstime. Those timestamps > are around the min a

Re: [JDBC] [BUGS] BUG #1780: JDBC driver "setNull" throws for BLOB

On Fri, 22 Jul 2005, Kris Jurka wrote: > On Fri, 22 Jul 2005, Andrus Adamchik wrote: > > > Whenver I call PreparedStatement.setNull(int, int) on BLOB or CLOB columns, > > an exception below occurs. Driver version: postgresql-8.0-310.jdbc3.jar. But > > looks like latest CVS version has the same

Re: [BUGS] BUG #1780: JDBC driver "setNull" throws for BLOB and CLOB

On Fri, 22 Jul 2005, Andrus Adamchik wrote: > Bug reference: 1780 > PostgreSQL version: 8.0.1 > Description:JDBC driver "setNull" throws for BLOB and CLOB columns > Details: > > Whenver I call PreparedStatement.setNull(int, int) on BLOB or CLOB columns, > an exception below occurs

Re: [BUGS] abstime bug

Bruce Momjian writes: > Michael Fuhr wrote: >> I'd guess this is due to the 32-bitness of abstime. Those timestamps >> are around the min and max values of a 32-bit timestamp based on the >> traditional Unix epoch. > Yea, I see the same thing in 8.0.X. I don't think abstime should be > used in

Re: [BUGS] BUG #1723: array_cat() bug when passed empty array

Dave Chapeskie <[EMAIL PROTECTED]> writes: > On Mon, Jun 20, 2005 at 03:44:24PM -0400, Tom Lane wrote: >> This makes it perfectly clear that the problem is that exec_assign_value >> must copy the given value before it frees the old, just in case they're >> the same. (Hmm, I wonder if we can shortc

Re: [BUGS] abstime bug

Michael Fuhr wrote: > On Fri, Jul 22, 2005 at 10:15:40AM -0400, Bruce Momjian wrote: > > > > Current CVS shows: > > > > test=> select '1901/12/14 1:00'::abstime; > > abstime > > > > 1901-12-14 01:00:00-05 > > (1 row) > > Depends on your timez

Re: [BUGS] abstime bug

On Fri, Jul 22, 2005 at 10:15:40AM -0400, Bruce Momjian wrote: > > Current CVS shows: > > test=> select '1901/12/14 1:00'::abstime; > abstime > >1901-12-14 01:00:00-05 > (1 row) Depends on your timezone: SET TimeZone TO 'US/Easter

Re: [BUGS] abstime bug

jw wrote: > # select '1901/12/14 1:00'::abstime; > abstime > > 2038-01-19 07:22:24+08 > (1 row) Current CVS shows: test=> select '1901/12/14 1:00'::abstime; abstime 1901-12-14 01:00:00-05

Re: [BUGS] Postmaster already running !!!

 Hi,   only remove postmaster.pid (NO clean up)   good look.     Jhon Carrillojdigital (a) cantv.net Caracas - Venezuela - Original Message - From: Sivaraman K.G To: pgsql-bugs@postgresql.org Sent: Friday, July 22, 2005 2:30 AM Subject: [BUGS] Postmaster already runn

[BUGS] abstime bug

# select '1901/12/14 1:00'::abstime; abstime 2038-01-19 07:22:24+08 (1 row) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining co

[BUGS] Postmaster already running !!!

Hi, I am running PostgreSQL version 8.0 in Solaris 8. I am starting the postmaster when the system is coming up. I am facing the following problem : FATAL:  lock file "/data/ALAsm/PGSQL/data/postmaster.pid" already exists HINT:  Is another postmaster (PID 448) running in data directory "/data/ALA

[BUGS] BUG #1779: psql.exe doesn't promt for password yet password authentication fails

The following bug has been logged online: Bug reference: 1779 Logged by: Jon Rylands Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Windows XP SP2 Description:psql.exe doesn't promt for password yet password authentication fails Details:

[BUGS] BUG #1780: JDBC driver "setNull" throws for BLOB and CLOB columns

The following bug has been logged online: Bug reference: 1780 Logged by: Andrus Adamchik Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Mac OS X 10.4 Description:JDBC driver "setNull" throws for BLOB and CLOB columns Details: Whenver I