| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Satoshi Nagayasu <snaga(at)uptime(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Michael Paquier <mpaquier(at)vmware(dot)com> |
| Subject: | Re: pg_rewind in contrib |
| Date: | 2015-01-14 10:01:31 |
| Message-ID: | 20150114100131.GI5245@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-01-09 10:48:39 +0200, Heikki Linnakangas wrote:
> It would nevertheless be handy to be able to do more stuff in a replication
> connection. For example, you might want to run functions like
> pg_create_restore_point(), pg_xlog_replay_pause/resume etc. in a replication
> connection. We should extend the replication protocol to allow such things.
> I'm not sure what it would look like; we can't run arbitrary queries when
> not being connected to a database, or arbitrary functions, but there are a
> lot of functions that would make sense.
Well, it's possible now to have replication connections connect to a
database if you choose now (replication=database dbname=...). We could
just add e.g. the fastpath function interface and add allow a couple of
builtin functions to be called. That'd probably be fairly simple.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-01-14 10:06:07 | Re: pg_rewind in contrib |
| Previous Message | Andres Freund | 2015-01-14 09:53:40 | Re: pg_rewind in contrib |