| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Function to move the position of a replication slot |
| Date: | 2017-08-16 16:24:11 |
| Message-ID: | 9551c0d4-6ad3-9ddc-4778-f36696672b2d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/4/17 08:05, Magnus Hagander wrote:
> PFA a patch that adds a new function, pg_move_replication_slot, that
> makes it possible to move the location of a replication slot without
> actually consuming all the WAL on it.
The name keeps confusing me. I understand "move" to be "rename" or
possibly "move it elsewhere", but not "move around in". I understand
that there is an analogy with FETCH/MOVE in cursors, but it's still
confusing.
I would also like to see some documentation for a use case of this.
Anyway, as discussed elsewhere in this thread, this patch needs several
changes.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-08-16 16:31:14 | Garbled comment in postgresGetForeignJoinPaths |
| Previous Message | Robert Haas | 2017-08-16 16:17:31 | Re: [COMMITTERS] pgsql: Simplify plpgsql's check for simple expressions. |