Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: InitPostgres and flatfiles question
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Bruce Momjian <bruce(at)momjian(dot)us>
- Cc: elein <elein(at)varlena(dot)com>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: InitPostgres and flatfiles question
- Date: Sat, 06 Jan 2007 21:11:44 -0500
- Message-id: <1983.1168135904@sss.pgh.pa.us> <text/plain>
Bruce Momjian <bruce(at)momjian(dot)us> writes: > We aren't going to disable that --- we are considering disabling the > backend from treating it as a single transaction. Or even more specifically, making sure that that only happens if you explicitly put begin/commit into the -c string. One thing I think we probably ought *not* change is that if any of the statements fail the rest of the -c string is abandoned --- that is, -c would work like a script with ON_ERROR_STOP enabled. regards, tom lane
- References:
- Re: InitPostgres and flatfiles question
- From: Bruce Momjian
- Re: InitPostgres and flatfiles question
- Prev by Date: Re: pg_ctl options
- Next by Date: Re: [PATCHES] COPY with no WAL, in certain circumstances
- Previous by thread: Re: InitPostgres and flatfiles question
- Next by thread: Re: InitPostgres and flatfiles question
- Indexes: