--On 16. Januar 2011 21:53:47 +0100 Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Is walreceiver something that the average DBA is going to realize
what it is? Perhaps go for something like replication slave?
I think walreceiver is very good here, and the user is already
confronted to
On Mon, Jan 17, 2011 at 04:05, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Jan 17, 2011 at 11:16 AM, Robert Haas robertmh...@gmail.com wrote:
On Sun, Jan 16, 2011 at 3:53 PM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Magnus Hagander mag...@hagander.net writes:
Is walreceiver
On Mon, Jan 17, 2011 at 10:57, Magnus Hagander mag...@hagander.net wrote:
On Mon, Jan 17, 2011 at 04:05, Fujii Masao masao.fu...@gmail.com wrote:
diff --git a/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c
b/src/backend/replication/libpqwalreceiver/libpqwalreceiv
index
Fujii Masao masao.fu...@gmail.com writes:
http://www.postgresql.org/docs/9.0/interactive/runtime-config-wal.html#GUC-MAX-WAL-SENDERS
+1 though I could not find the mention to walreceiver in the doc.
True, we already use wal sender, I should have said similar phrasing.
Regards,
--
Dimitri
Since we now show the application name in pg_stat_replication, I think
it would make sense to have the walreceiver set
fallback_application_name on the connection string, like so:
diff --git a/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c
Magnus Hagander mag...@hagander.net writes:
Since we now show the application name in pg_stat_replication, I think
it would make sense to have the walreceiver set
fallback_application_name on the connection string, like so:
Seems reasonable, but postgres is a mighty poor choice of name
for
On Sun, Jan 16, 2011 at 17:29, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
Since we now show the application name in pg_stat_replication, I think
it would make sense to have the walreceiver set
fallback_application_name on the connection string, like so:
Magnus Hagander mag...@hagander.net writes:
Is walreceiver something that the average DBA is going to realize
what it is? Perhaps go for something like replication slave?
I think walreceiver is very good here, and the user is already
confronted to such phrasing.
On Sun, Jan 16, 2011 at 3:53 PM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Magnus Hagander mag...@hagander.net writes:
Is walreceiver something that the average DBA is going to realize
what it is? Perhaps go for something like replication slave?
I think walreceiver is very good here, and
On Mon, Jan 17, 2011 at 11:16 AM, Robert Haas robertmh...@gmail.com wrote:
On Sun, Jan 16, 2011 at 3:53 PM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Magnus Hagander mag...@hagander.net writes:
Is walreceiver something that the average DBA is going to realize
what it is? Perhaps go for
10 matches
Mail list logo
