there is no logical point to call spi_freeplan()
Will the plan be freed when the db session / connection closes OR
Will it lead to any memory leaks ?
Thanks
Anupama.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ger invocation.
In effect, there is no logical point to call spi_freeplan()
Will the plan be freed when the db session / connection closes
Will it lead to any memory leaks (typically my db connections are open for long
time ) ?
Thanks
Anupama.
--
Sent via pgsql-general mailing list (pgs
transactions that occurred between t1 and t2.
Regards,
Anupama.
t soon after "touch /tmp/pgsql.failover" OR should I
wait till the secondary has finished replaying all the delivered stream ?
c) How do I know if the replay is over and it is ready for a standalone
operation ?
Thanks for your help
Anupama.
the transactions. Of course the WAL will be
available on a shared storage volume. If this is possible, what exactly do I
need in my configuration files - postgresql.conf, recovery.conf ?
Thanks for your help
Anupama.
Thanks so much. That clarifies.
-Anupama
On Monday, April 14, 2014 12:09 PM, Michael Paquier
wrote:
On Sat, Apr 12, 2014 at 3:12 PM, Anupama Ramaswamy wrote:
> Lets suppose at this point there is 0 delivery lag but bytes of replay
> lag.
>
All your answers are h
help.
On Monday, April 14, 2014 1:35 PM, Albe Laurenz wrote:
Anupama Ramaswamy wrote:
> I would like to setup a 2 servers with streaming replication, one master and
> another hot standby.
> I want to use the standby for read-only queries. So I want the replication
> lag to be
Hi,
I'm using the pg_dump and pg_restore client applications to implement
our database backup-restore strategies. Wrt this, inorder to be able to
autoamate the backup process (run it as a cron job), I'm using the
.pgpass file for automating the password input. This is working for
pg_dump.
My res
