=?ISO-8859-1?Q?Fabr=EDzio_de_Royes_Mello?= fabriziome...@gmail.com writes:
2012/3/14 Tom Lane t...@sss.pgh.pa.us
For most people it won't
matter, but for people who are using the feature, it seems like
important information. Per the OP's complaint, it's particularly
important for those who
Hi,
I have a hard time figuring out why my replication stopped with a message like
FATAL: password authentication failed for user foo
in the logs. I thought it was some pg_hba.conf change, a pgpass modification,
or NOLOGIN option, it wasn't. I was out of options when I remembered to check
if
On Wed, Mar 14, 2012 at 11:20:05AM -0300, Euler Taveira de Oliveira wrote:
Hi,
I have a hard time figuring out why my replication stopped with a message like
FATAL: password authentication failed for user foo
in the logs. I thought it was some pg_hba.conf change, a pgpass modification,
2012/3/14 David Fetter da...@fetter.org
I don't know how frequently people use VALID UNTIL, but I'm guessing
it's not terribly often because yours is the first comment about how
it's not exposed, so I'd tend toward putting it in attributes rather
than a separate column.
If it's desired I
2012/3/14 David Fetter da...@fetter.org
I don't know how frequently people use VALID UNTIL, but I'm guessing
it's not terribly often because yours is the first comment about how
it's not exposed, so I'd tend toward putting it in attributes rather
than a separate column.
The attached patch
=?ISO-8859-1?Q?Fabr=EDzio_de_Royes_Mello?= fabriziome...@gmail.com writes:
The attached patch put VALID UNTIL into attributes column in verbose mode
like example above.
Why would you confine it to verbose mode? For most people it won't
matter, but for people who are using the feature, it seems
2012/3/14 Tom Lane t...@sss.pgh.pa.us
Why would you confine it to verbose mode?
Because I did not want to change the current behavior of this psql
command... but...
For most people it won't
matter, but for people who are using the feature, it seems like
important information. Per the
