| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: I am done |
| Date: | 2002-09-02 23:55:48 |
| Message-ID: | 28633.1031010948@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Perhaps one should consider removing the autocommit option. It's no use
> if it's there but everything breaks when you turn it on.
As far as I'm concerned, it's in there for one reason only (as far as
7.3 goes): so that we can run the NIST SQL compliance tests. Anyone who
wants to use it in production at this point is doing so at their own
risk.
In practice, as long as we fix libpq's startup SET commands, the major
problems will just be with large object support, which is not mainstream
usage either; so I'm prepared to live with it for a release or so. It's
not like there aren't any other combinations of PG features that don't
play nice together.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-03 00:00:40 | Re: Future of --enable-recode? |
| Previous Message | Tom Lane | 2002-09-02 23:50:56 | Re: reindex of toast tables |