| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql default options |
| Date: | 2007-04-27 17:09:12 |
| Message-ID: | CCB2F686-5AEB-424B-A96D-F47B4F2000FC@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 27, 2007, at 12:44 AM, Tom Lane wrote:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> I would like to suggest that we make psql default when in
>> interactive mode to
>> using AUTOCOMMIT=false and ON_ERROR_ROLLBACK=true.
>
> That is *way* too big a behavioral change to make depend on
> something as
> fragile as whether psql thinks it's interactive or not.
What about at least documenting it as a recommended practice? I agree
with Greg that it's a really good way to operate...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2007-04-27 17:33:06 | Re: too much WAL volume |
| Previous Message | Joshua D. Drake | 2007-04-27 16:51:05 | Re: Windows installer for 8.3 - dev release for testing |