Re: [PATCHES] pg_restore ignore error patch

I looked over the patch and it seems to continue on pg_restore errors by default. That isn't good. By default, any error should make it exit loudly. I'm not sure of that. pg_dump is really designed and tested for the case of text dump to a psql script, and if there is an error

Re: [PATCHES] Basic subtransaction facility

Alvaro Herrera [EMAIL PROTECTED] writes: I'm thinking that I'll to add a new elog level to signal a can't-happen condition within the transaction machinery, which would abort the whole transaction tree (more than ERROR) but would not take the whole backend down (less than FATAL). What should

Re: [PATCHES] pg_restore ignore error patch

Fabien COELHO wrote: I looked over the patch and it seems to continue on pg_restore errors by default. That isn't good. By default, any error should make it exit loudly. I'm not sure of that. pg_dump is really designed and tested for the case of text dump to a psql

[PATCHES] NetBSD 2.0 / native threads

Hi! Starting with 2.0 NetBSD has native threads. The attached patch adds support for this to the src/templates/netbsd file. (Since, $host_os doesn't include the OS version number I had to take $build.) Please CC me in your replies since I'm not subscribed to this list. Cheers, Marc $NetBSD$

Re: [PATCHES] NetBSD 2.0 / native threads

OK, added. I will be overhauling the thread flags for 7.5 so will make sure this is included. Thanks. --- Marc Recht wrote: -- Start of PGP signed section. Hi! Starting with 2.0 NetBSD has native threads. The attached

Re: [PATCHES] CSV patch applied

CSV - enable CSV mode QUOTE - specify quote character ESCAPE - specify escape character FORCE - force quoting of specified columns FORCE QUOTE QUOTING col1,col2? QUOTED col1,col2? IN QUOTES col1,cold LITERAL - prevent NULL checks for specific

Re: [PATCHES] CSV patch applied

Fabien COELHO wrote: CSV - enable CSV mode QUOTE - specify quote character ESCAPE - specify escape character FORCE - force quoting of specified columns FORCE QUOTE QUOTING col1,col2? QUOTED col1,col2? IN QUOTES col1,cold LITERAL -

[PATCHES] NEXT VALUE FOR...

It would appear the spec was approved of before we got foo.nextval, so here it is again. NEXT VALUE FOR and CURRENT VALUE FOR where CURRENT is an unreserved keyword and VALUE is not reserved in any way (ident with comparison to value). This allows the default of a table to depend on a sequence,

Re: [PATCHES] PSQLRC environment variable.

Bruce Momjian wrote: Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: I just checked a few apps and I see they usually allow a global config file to be specified. How about SYSPSQLRC that adds a system-wide psql config file to be read before the one in the home directory?