| From: | Joachim Wieland <joe(at)mcknight(dot)de> |
|---|---|
| To: | Florian Weimer <fweimer(at)bfk(dot)de> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: synchronized snapshots |
| Date: | 2011-08-15 11:30:10 |
| Message-ID: | CACw0+10Xu5hMwJ3ZLMFY8HDdeLAqJbhdnmyTwdZrxqam6dWONg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 15, 2011 at 6:41 AM, Florian Weimer <fweimer(at)bfk(dot)de> wrote:
> * Simon Riggs:
>
>> I don't see the need to change the BEGIN command, which is SQL
>> Standard. We don't normally do that.
>
> Some language bindings treat BEGIN specially, so it might be difficult
> to use this feature.
It's true, the command might require explicit support from language
bindings. However I used some perl test scripts, where you can also
send a START TRANSACTION command in an $dbh->do(...).
The intended use case of this feature is still pg_dump btw...
Joachim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-08-15 11:50:58 | Re: pg_stat_replication vs StandbyReplyMessage |
| Previous Message | Joachim Wieland | 2011-08-15 11:23:29 | Re: synchronized snapshots |