Re: [BUGS] BUG #2289: insert into tables not working

2006-02-28 Thread Michael Fuhr
[Please copy the mailing list on replies.] On Wed, Mar 01, 2006 at 08:55:29AM -0800, Abhilash Krishnan wrote: > ya the transactions are commited also no error has been shown in any > of the operations How are you determining that data isn't getting inserted? If you do a select in the

Re: [BUGS] FATAL: semctl(1672698088, 12, SETVAL, 0) failed

2006-02-28 Thread Qingqing Zhou
On Tue, 28 Feb 2006, Bruce Momjian wrote: > > Uh, how do we handle it now? I thought we did just that. > > OK, so how do we find the answer? > For both problems, I am uncertain (or I've sent a patch already :-(). Call more artillery support here ... Regards, Qingqing

Re: [BUGS] FATAL: semctl(1672698088, 12, SETVAL, 0) failed

2006-02-28 Thread Bruce Momjian
Qingqing Zhou wrote: > > "Bruce Momjian" wrote > > > In port/win32.h, we have > > > > > > #undef EAGAIN > > > #undef EINTR > > > #define EINTR WSAEINTR > > > #define EAGAIN WSAEWOULDBLOCK > > > > > > What's the rationale of doing so? > > > > We did this so that our code could refer to EINTR/EAGAI

[BUGS] BUG #2291: int2vectorrecv() and oidvectorrecv() are wrong (SIGBUS)

2006-02-28 Thread Tim Kordas
The following bug has been logged online: Bug reference: 2291 Logged by: Tim Kordas Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: All Description:int2vectorrecv() and oidvectorrecv() are wrong (SIGBUS) Details: During Greenplum's ongoi

Re: [BUGS] FATAL: semctl(1672698088, 12, SETVAL, 0) failed

2006-02-28 Thread Qingqing Zhou
"Bruce Momjian" wrote > > In port/win32.h, we have > > > > #undef EAGAIN > > #undef EINTR > > #define EINTR WSAEINTR > > #define EAGAIN WSAEWOULDBLOCK > > > > What's the rationale of doing so? > > We did this so that our code could refer to EINTR/EAGAIN without > port-specific tests. > AFAICS, b

Re: [BUGS] FATAL: semctl(1672698088, 12, SETVAL, 0) failed

2006-02-28 Thread Bruce Momjian
Qingqing Zhou wrote: > I encountered an error when I fast shutdown 8.1.1 on Win2k: > > FATAL: semctl(1672698088, 12, SETVAL, 0) failed: A blocking operation > was interrupted by a call to WSACancelBlockingCall. > > A similar error on 8.1/win2003 was reported on pgsql-general (sorry, I c

Re: [BUGS] BUG #2290: Incorrect sequence increment after backup/restore

2006-02-28 Thread Tom Lane
"Oleg Mamontov" <[EMAIL PROTECTED]> writes: > If after CREATE TABLE with SERIAL column i'll change sequence increment to 2 > or some other value (with ALTER SEQUENCE) then always work correctly (all > inserted rows will have values incremented by 2). We currently consider that a serial column is a

Re: [BUGS] BUG #2289: insert into tables not working

2006-02-28 Thread Michael Fuhr
On Tue, Feb 28, 2006 at 09:24:35AM +, Abhilash Krishnan wrote: > I am having an application using java, jsp, struts and hibernate with a > backend of postgresql. Here, during some operations, although the insert > query is generated by hibernate and can be seen in the console, the data is > not

[BUGS] BUG #2290: Incorrect sequence increment after backup/restore

2006-02-28 Thread Oleg Mamontov
The following bug has been logged online: Bug reference: 2290 Logged by: Oleg Mamontov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.x/8.1.x Operating system: FreeBSD 4.x,5.x,6.x Description:Incorrect sequence increment after backup/restore Details: If af

Re: [BUGS] BUG #2286: Wrong index creation with cs_CZ locales and

2006-02-28 Thread David Sauer
No, the database was initialized new. initdb -D /var/lib/pg-8.1.3 -E latin2 I have isolated problem to new locale definition file - glibc 2.3.6 with cs_CZ definition file from 2.3.2 works ok and raises if data contain '-'. I'am still not sure if problem is in postgres (bad work with locale data)

[BUGS] BUG #2288: bad value for type timestamp using JDBC Type2 Driver version 8.1-405

2006-02-28 Thread Jonathan Albert C. Vallar
The following bug has been logged online: Bug reference: 2288 Logged by: Jonathan Albert C. Vallar Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: Centronix Linux Description:bad value for type timestamp using JDBC Type2 Driver version 8.

[BUGS] BUG #2289: insert into tables not working

2006-02-28 Thread Abhilash Krishnan
The following bug has been logged online: Bug reference: 2289 Logged by: Abhilash Krishnan Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.2 Operating system: windows 2000 Description:insert into tables not working Details: I am having an application using