| From: | Marcin Mańk <marcin(dot)mank(at)gmail(dot)com> |
|---|---|
| To: | Markus Wanner <markus(at)bluegap(dot)ch> |
| Cc: | Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: synchronized snapshots |
| Date: | 2010-01-09 20:44:38 |
| Message-ID: | F5D22F22-CF0B-4709-85FE-83325BF2C02D@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dnia 2010-01-09 o godz. 20:37 Markus Wanner <markus(at)bluegap(dot)ch> napisał
(a):
> Hi
>
> Joachim Wieland wrote:
>> Since nobody objected to the idea in general, I have implemented it.
How cool it would be if we could synchronize snapshots between the
master and the (sr) standby?
The connection poolers could use that to send read-only queries to the
standby, and when the first dml/ddl statement in a transaction comes
up, they could switch to the master.
If it is hard to tell from the statement if it writes anything, the
pooler could catch the error, and retry on the master
Regards
Marcin Mańk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2010-01-09 20:53:54 | Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function |
| Previous Message | Tom Lane | 2010-01-09 20:28:11 | Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function |