| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <jim(at)nasby(dot)net>, Joachim Wieland <joe(at)mcknight(dot)de>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: synchronized snapshots |
| Date: | 2011-08-17 01:54:44 |
| Message-ID: | 1313546084.23102.5.camel@jdavis-ux.asterdata.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2011-08-16 at 21:08 -0400, Robert Haas wrote:
> attaching it to BEGIN feels natural to me.
My only objection is that people have different expectations about
whether the session will remain in a transaction block when they
encounter an error. So, it's hard to make this work without surprising
about half the users.
And there are some fairly significant consequences to users who guess
that they will remain in a transaction block in case of an error; or who
are just careless and don't consider that an error may occur.
> If we did add another toplevel command, what would we call it?
"SET TRANSACTION SNAPSHOT" perhaps?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Abbate | 2011-08-17 02:00:59 | Re: Finding tables dropped by DROP TABLE CASCADE |
| Previous Message | Jeff Davis | 2011-08-17 01:44:56 | Re: synchronized snapshots |