I have observed that currently incase there is a network break between
master and standby, walsender process gets terminated immediately, however
walreceiver detects the breakage after long time.
The main reason I could see is due to replication_timeout configuration
parameter, walsender checks
On Tuesday, September 04, 2012 6:55 PM Amit kapila wrote:
On Tuesday, September 04, 2012 12:42 AM Jeff Janes wrote:
On Mon, Sep 3, 2012 at 7:15 AM, Amit kapila amit.kap...@huawei.com wrote:
This patch is based on below Todo Item:
Consider adding buffers the background writer finds reusable to
On Tue, Sep 04, 2012 at 09:46:58AM -0700, Daniel Farina wrote:
I might try to find the segments leading up to the overflow point and
try xlogdumping them to see what we can see.
That would be helpful to see.
Just to grasp at yet-flimsier straws, could you post (URL preferred, else
private
Excerpts from Andrew Dunstan's message of jue sep 06 00:33:35 -0300 2012:
On 09/05/2012 11:01 PM, Stephen Frost wrote:
* Andrew Dunstan (and...@dunslane.net) wrote:
Now that you've provided the magic sauce wrt --skip-steps, can we get an
admin to implement a doc-only build that runs more
Below mentioned issue might be current behavior of PostgreSQL, but I am not
able to find that in documentation so I have done brief analysis as well.
Issue: cascade standby server raise errors as “FATAL: the database system
is starting up” when trying to connect a client. Cascaded standby
Here's a prettified version of this stuff. I found one bug in the macro
ilist_s_head: the test was reversed. Also, curiously, the macro had the
same name as the struct, so I renamed the macro. I take it you haven't
used this macro, so maybe it shouldn't be there at all? Or maybe I
completely
On 9/6/12 7:06 AM, Amit Kapila wrote:
1.Set up postgresql-9.2beta2 on all hosts.
Did you retest this with 9.2rc1? Beta2 was a while ago
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Thu, Sep 6, 2012 at 12:09 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Here's a prettified version of this stuff. I found one bug in the macro
ilist_s_head: the test was reversed. Also, curiously, the macro had the
same name as the struct, so I renamed the macro. I take it you
On Wed, 2012-09-05 at 17:03 -0400, Tom Lane wrote:
In general I think the selling point for such a feature would be no
administrative hassles, and I believe that has to go not only for the
end-user experience but also for the application-developer experience.
If you have to manage
On Tue, Sep 4, 2012 at 5:30 AM, Etsuro Fujita
fujita.ets...@lab.ntt.co.jp wrote:
I noticed the syntax of the \copy command in the psql reference page is an old
style. ISTM it's better to update the document. Please find attached a
patch.
Seems reasonable to me. Committed.
--
Robert Haas
On 08/20/2012 01:26 PM, Tom Lane wrote:
Fujii Masao masao.fu...@gmail.com writes:
OK. Attached patch fixes the problem as you suggested, i.e., it backs up
endword if the second loop exits in an escape pair.
Applied with a bit of further adjustment of the comments. Thanks!
Andrew Dunstan and...@dunslane.net writes:
On 08/20/2012 01:26 PM, Tom Lane wrote:
Fujii Masao masao.fu...@gmail.com writes:
OK. Attached patch fixes the problem as you suggested, i.e., it backs up
endword if the second loop exits in an escape pair.
Applied with a bit of further adjustment
On Mon, Sep 3, 2012 at 2:19 AM, togetinfo mail togetinfom...@gmail.com wrote:
We are trying to introduce a thread that monitors the creation of the
trigger_file. As and when the file is created, the process that monitors
postgres server needs to be notified through the inotify API.
This is to
On 09/06/2012 05:09 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 08/20/2012 01:26 PM, Tom Lane wrote:
Fujii Masao masao.fu...@gmail.com writes:
OK. Attached patch fixes the problem as you suggested, i.e., it backs up
endword if the second loop exits in an escape pair.
I have developed a patch to make the python3 regression test setup a bit
simpler. Currently, we are making mangled copies of
plpython/{expected,sql} to plpython/python3/{expected,sql}, and run the
tests in plpython/python3. This has the disadvantage that the
regression.diffs file, if any, ends
Excerpts from Peter Eisentraut's message of jue sep 06 21:33:33 -0300 2012:
I have developed a patch to make the python3 regression test setup a bit
simpler. Currently, we are making mangled copies of
plpython/{expected,sql} to plpython/python3/{expected,sql}, and run the
tests in
I wrote:
Attached is a draft patch against HEAD for this.
I've finished back-porting this. I'm not going to commit it until 9.2.0
is definitely gold, but attached is the 9.1 version of the patch, if
you'd like to try it and verify that it fixes your original problem.
I'm looking at the following code in pg_dump.c
/*
* Start transaction-snapshot mode transaction to dump consistent data.
*/
ExecuteSqlStatement(fout, BEGIN);
if (fout-remoteVersion = 90100)
{
if (serializable_deferrable)
ExecuteSqlStatement(fout,
18 matches
Mail list logo
