On 18 October 2017 at 02:01, Alexander Korotkov
<a.korotkov@postgrespro.ru> wrote:
> On Wed, Sep 6, 2017 at 4:42 PM, Alexander Korotkov
> <a.korotkov@postgrespro.ru> wrote:
>>
>> We're currently blocking writing queries on standby if even they are
>> modifying contents of foreign tables. But do we have serious reasons for
>> that?
>> Keeping in the mind FDW-sharding, making FDW-tables writable from standby
>> would be good to prevent single-master bottleneck.
>> I wrote simple patch enabling writing to foreign tables from standbys. It
>> works from the first glance for me.
>
>
> No interest yet, but no objections too :-)
> I'm going to add this to next commitfest.
Superficially at least, it sounds like a good idea.
We should only need a virtual xid when we're working with foreign
tables since we don't do any local heap changes.
How's it work with savepoints?
-- Craig Ringer http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers