Re: [BUGS] initdb fails on ultra2 sparc64, freebsd 5.4

2005-05-20 Thread Tom Lane
Andrew - Supernews <[EMAIL PROTECTED]> writes: > On 2005-05-21, Tom Lane <[EMAIL PROTECTED]> wrote: >> initdb does not use libpq ... it might link to it, > Linking to it is enough to bring in libc_r, and pick up libc_r's versions > of at least some system calls. The ktrace results show this. [ sh

Re: [BUGS] initdb fails on ultra2 sparc64, freebsd 5.4

2005-05-20 Thread Andrew - Supernews
On 2005-05-21, Tom Lane <[EMAIL PROTECTED]> wrote: > Andrew - Supernews <[EMAIL PROTECTED]> writes: >> The reason for the hang is that the sending end of the pipe from initdb >> to postgres is not being closed by popen(), so postgres never sees EOF >> on it. In this context I am suspicious of the f

Re: [BUGS] initdb fails on ultra2 sparc64, freebsd 5.4

2005-05-20 Thread Tom Lane
Andrew - Supernews <[EMAIL PROTECTED]> writes: > The reason for the hang is that the sending end of the pipe from initdb > to postgres is not being closed by popen(), so postgres never sees EOF > on it. In this context I am suspicious of the fact that while libpq is > being built with threading, th

Re: [BUGS] initdb fails on ultra2 sparc64, freebsd 5.4

2005-05-20 Thread Andrew - Supernews
On 2005-05-13, Tom Lane <[EMAIL PROTECTED]> wrote: > David Walker <[EMAIL PROTECTED]> writes: >> On a Sun ultra2 sparc64 initdb hangs here: > > Where's "here"? Build with --enable-debug, then attach to the stuck > process with gdb and get a stack trace. I've just done some analysis on this on Dav

Re: [BUGS] CHECK constraint (true) causes dumps with parse errors

2005-05-20 Thread Tom Lane
Neil Conway <[EMAIL PROTECTED]> writes: > Szűcs Gábor wrote: >> Check constraints: >> "foobar" CHECK () > Yeah, I can repro this with current REL7_4_STABLE sources, but it looks > fixed in HEAD and REL8_0_STABLE. I think the reason is that 7.4 applies make_ands_implicit before storing the constr

Re: [BUGS] BUG #1676: Statment order in rules

2005-05-20 Thread Olleg Samoylov
Tom Lane wrote: This isn't a bug. The DELETE causes the a=0 row to disappear from the I undestand. When I got choice between rules and triggers, I looked carefully is documantation, section "33.6. Rules versus Triggers". As I can see, rules prefered, there are many examples, why rules better then

Re: [BUGS] CHECK constraint (true) causes dumps with parse errors

2005-05-20 Thread Neil Conway
SzÅcs GÃbor wrote: # create table foo (bar int, constraint foobar check (true)); CREATE TABLE # \d foo Table "public.foo" Column | Type | Modifiers +-+--- bar| integer | Check constraints: "foobar" CHECK () Yeah, I can repro this with current REL7_4_STABLE

[BUGS] CHECK constraint (true) causes dumps with parse errors

2005-05-20 Thread Szűcs Gábor
Dear Gurus, Version: 7.3.3, 7.4.8 I don't know for sure, but something like this happened when dumping our server from 7.3 to 7.4. Actually, it seems to be a problem in 7.4 (maybe also in 7.3, but unlikely -- see below, "our original way"). # create table foo (bar int, constraint foobar check (t