Re: Streaming replication as a separate permissions
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>, Florian Pflug <fgp@phlo.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-12-27T21:42:09Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Allow Win32 to compile under MinGW. Major changes are:
- 12c942383296 7.4.1 cited
Magnus Hagander <magnus@hagander.net> writes: > Updated patch, still pending docs, but otherwise updated: allow > start/stop backup, make sure only superuser can turn on/off the flag, > include in system views, show properly in psql. I'd suggest avoiding creating the static cache variable AuthenticatedUserIsReplicationRole. This can't possibly be sufficiently interesting from a performance point of view to justify the risks associated with stale cache values. Just look up the pg_authid syscache entry when needed, ie, treat it more like rolcreaterole than rolsuper. BTW, you forgot pg_dumpall support. regards, tom lane