From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: Is anything preventing us from allowing write to foreign tables from standby? |
Date: | 2017-10-18 00:14:36 |
Message-ID: | CAMsr+YF9tQ4zfvLF6bsF7hDB0tNL4-Yvxc_A21h1pJpi+ifMwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18 October 2017 at 02:01, Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> On Wed, Sep 6, 2017 at 4:42 PM, Alexander Korotkov
> <a(dot)korotkov(at)postgrespro(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2017-10-18 00:43:43 | alter table doc fix |
Previous Message | Andres Freund | 2017-10-17 21:39:57 | Re: [POC] Faster processing at Gather node |