now you can only enable WAL archive on the Master server,it will not take
effect on replication server.
I can't find the doc which explicit prohibit WAL archive on the replication
server,and there are WAL generated in the slave pg_xlog dir with
archive_status subdir,so I think this may be a bug.
On Thu, Aug 8, 2013 at 1:52 PM, Vik Fearing vik.fear...@dalibo.com wrote:
Someone on IRC a while ago was complaining that there was no way to
specify an interval for pg_sleep, so I made one. Patch against today's
HEAD attached.
Usage: SELECT pg_sleep(interval '2 minutes');
I would add this
On 08/10/2013 04:26 AM, Greg Stark wrote:
On Sat, Aug 10, 2013 at 5:30 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Any other client would behave the same
if it were killed while waiting for some backend query. So the right
fix would involve figuring out a way for the backend to kill itself
if the
On Sun, Aug 11, 2013 at 9:25 PM, Josh Berkus j...@agliodbs.com wrote:
No, it's been a chronic issue since we got SMP support, pretty much
forever. Why do you think we have pg_terminate_backend()?
The problem, as explored downthread, is that there's no clear way to fix
this. It's a problem
On Tue, Aug 6, 2013 at 12:51 AM, Tom Lane t...@sss.pgh.pa.us wrote:
David Gudeman dave.gude...@gmail.com writes:
For those who don't want to go to the link to see what I'm talking
about with query rewrites, I thought I'd give a brief description.
Foreign data wrappers currently do all of
Hi all,
While playing a bit with background workers (commit 527ea66), I found that
setting bgw_main for a dynamic bgworker, as well as bgw_library_name and
bgw_library_name, crashes to server if the library defining the function
defined in bgw_main is not loaded. In order to reproduce that, for
