From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
Date: | 2018-01-09 02:36:59 |
Message-ID: | dd03f188-d5f2-0089-0bf6-7d3abe4169ad@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/3/18 15:13, Tomas Vondra wrote:
> Forgot to mention that the v4 also extends the CREATE SUBSCRIPTION to
> allow customizing the streaming and memory limit. So you can do
>
> CREATE SUBSCRIPTION ... WITH (streaming=on, work_mem=1024)
>
> and this subscription will allow streaming, and the logica_work_mem (on
> provider) will be set to 1MB.
I was wondering already during PG10 development whether we should give
subscriptions a generic configuration array, like databases and roles
have, so we don't have to hardcode a bunch of similar stuff every time
we add an option like this. At the time we only had synchronous_commit,
but now we're adding more.
Also, instead of sticking this into the START_REPLICATION command, could
we just run a SET command? That should work over replication
connections as well.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-01-09 02:46:21 | refactor subscription tests to use PostgresNode's wait_for_catchup |
Previous Message | Peter Eisentraut | 2018-01-09 02:24:55 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |