| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Single-Transaction Utility options |
| Date: | 2005-12-18 18:55:26 |
| Message-ID: | 1134932126.2964.187.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Sat, 2005-12-17 at 20:03 +0100, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > Changes as discussed. "singletransaction.patch" attached.
>
> I meant to ask, why is this not the default or only behavior?
Historically, it didn't work that way, so I hadn't thought to change
that behaviour. We could I suppose... but I'm happy with just an option
to do --single-transaction.
> Your
> patch does not contain a documentation update, and so the user has no
> information about why to use this option or not.
I was waiting for tech approval of the patch before writing the docs. A
doc patch is enclosed.
Best Regards, Simon Riggs
| Attachment | Content-Type | Size |
|---|---|---|
| 1doc.patch | text/x-patch | 1.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-18 19:04:53 | Re: Single-Transaction Utility options |
| Previous Message | Volkan YAZICI | 2005-12-18 10:13:17 | tuple count and v3 functions in psql for COPY |