On Tue, Jan 22, 2013 3:27 PM Hari Babu wrote:
On Saturday, January 19, 2013 5:49 PM Magnus Hagander wrote:
On Fri, Jan 18, 2013 at 1:05 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
On 18.01.2013 13:41, Amit Kapila wrote:
On Friday, January 18, 2013 3:46 PM Heikki Linnakangas wrote:
On Saturday, January 19, 2013 5:49 PM Magnus Hagander wrote:
On Fri, Jan 18, 2013 at 1:05 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
On 18.01.2013 13:41, Amit Kapila wrote:
On Friday, January 18, 2013 3:46 PM Heikki Linnakangas wrote:
On 18.01.2013 08:50, Amit Kapila wrote:
So to
On Sat, Jan 19, 2013 at 12:33 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Dimitri Fontaine dimi...@2ndquadrant.fr writes:
On the other hand, discrepancies in between command line arguments
processing in our tools are already not helping our users (even if
pg_dump -d seems to have been fixed along
Robert Haas wrote:
I heartily agree. I can say from firsthand experience that when minor
releases break things for customers (and they do), the customers get
*really* cranky. Based on recent experience, I think we should be
tightening our standards for what gets back-patched, not loosening
On Fri, Jan 18, 2013 at 1:05 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
On 18.01.2013 13:41, Amit Kapila wrote:
On Friday, January 18, 2013 3:46 PM Heikki Linnakangas wrote:
On 18.01.2013 08:50, Amit Kapila wrote:
I think currently user has no way to specify TCP keepalive
On Fri, Jan 18, 2013 at 2:43 PM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Heikki Linnakangas hlinnakan...@vmware.com writes:
You could still use environment variables and a service file to do it, but
it's certainly more cumbersome. It clearly should be possible to pass a full
connection
Magnus Hagander mag...@hagander.net writes:
FWIW, +1. I would consider it a bugfix (backpatch, etc).
While it's a feature I'd very much like to see, I really don't think
you can consider it a bugfix. It's functionality that was left out -
it's not like we tried to implement it and it didn't
Tom Lane t...@sss.pgh.pa.us writes:
I don't think that argument holds any water at all. There would still
be differences in command line argument capabilities out there ---
they'd just be between minor versions not major ones. That's not any
easier for people to deal with. And what will you
On 18.01.2013 08:50, Amit Kapila wrote:
I think currently user has no way to specify TCP keepalive settings from
pg_basebackup, please let me know if there is any such existing way?
I was going to say you can just use keepalives_idle=30 in the
connection string. But there's no way to pass a
On Friday, January 18, 2013 3:46 PM Heikki Linnakangas wrote:
On 18.01.2013 08:50, Amit Kapila wrote:
I think currently user has no way to specify TCP keepalive settings
from
pg_basebackup, please let me know if there is any such existing way?
I was going to say you can just use
On 18.01.2013 13:41, Amit Kapila wrote:
On Friday, January 18, 2013 3:46 PM Heikki Linnakangas wrote:
On 18.01.2013 08:50, Amit Kapila wrote:
I think currently user has no way to specify TCP keepalive settings
from
pg_basebackup, please let me know if there is any such existing way?
I was
On Friday, January 18, 2013 5:35 PM Heikki Linnakangas wrote:
On 18.01.2013 13:41, Amit Kapila wrote:
On Friday, January 18, 2013 3:46 PM Heikki Linnakangas wrote:
On 18.01.2013 08:50, Amit Kapila wrote:
I think currently user has no way to specify TCP keepalive settings
from
Heikki Linnakangas hlinnakan...@vmware.com writes:
You could still use environment variables and a service file to do it, but
it's certainly more cumbersome. It clearly should be possible to pass a full
connection string to pg_basebackup, that's an obvious oversight.
FWIW, +1. I would consider
13 matches
Mail list logo
