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 dir

[PATCHES] CSV keyword change

I just changed the COPY CSV keywords: FORCE QUOTE to force quotes FORCE NOT NULL to quote null input values Patch attached. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive,

[PATCHES] Change of CSV keywords

I just changed COPY CSV keywords to be: FORCE QUOTE to force quotes on output FORCE NOT NULL to quote null input values -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive,

[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] 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

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

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 attach

[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] CSV patch applied

Peter Eisentraut wrote: Bruce Momjian wrote: I have applied the attached patch that complete TODO item: o -Allow dump/load of CSV format This adds new keywords to COPY and \copy: CSV - enable CSV mode QUOTE - specify quote character ESCAPE - specify escape charact

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

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 sh

Re: [PATCHES] CSV patch applied

Bruce Momjian wrote: > I have applied the attached patch that complete TODO item: > > o -Allow dump/load of CSV format > > This adds new keywords to COPY and \copy: > > CSV - enable CSV mode > QUOTE - specify quote character > ESCAPE - specify escape character >

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