my postgresql-9.0-main.log log file is 0 bytes. Postgres user has perms to
write to it. And and postgresql.conf file shows to log, but it's not. Not
sure why.
I have the defaults set in except for these changes:
log_connections = on
log_disconnections = on
log_duration = off
log_line_prefix =
restart or rather
reload of the config file. Also when I did an LSOF of the file, nothing
was locking it ... ie usually postgres would be the one, but not in this
case.
On Thu, Jan 24, 2013 at 12:39 PM, Adrian Klaver wrote:
> On 01/24/2013 09:29 AM, Anson Abraham wrote:
>
>> my postgr
t;.
it's a head scratcher for me.
On Thu, Jan 24, 2013 at 4:08 PM, Adrian Klaver wrote:
> On 01/24/2013 12:44 PM, Anson Abraham wrote:
>
>> i've always had logging_collector off. it would still log query /
>> transactions that failed to the "syslog"
>&
ng of the instance, but that's something I
don't have luxury of doing until the next maintanence window, which will be
a ways in the future.
Thanks,
-Anson
On Fri, Jan 25, 2013 at 3:35 PM, Adrian Klaver wrote:
> On 01/25/2013 09:00 AM, Anson Abraham wrote:
>
>> identical
My postgresql-9.0-main.log file has suddenly stopped getting updated. I do
not know why it stopped all of a sudden. We made a slight modification
where changed in the postgresql.conf param:
From
log_connections = off
log_disconnections = off
To
log_connections = on
log_disconnections = on
I'm
nd did a reload, postgres created
the log file. So not sure what is going on exactly.
Again, any help would be appreciated here to figure this out, where I don't
need to restart the db.
Thanks
On Thu, Feb 28, 2013 at 11:19 AM, Anson Abraham wrote:
> My postgresql-9.0-main.log file has sud
how is that different from
/etc/init.d/postgres reload or for that matter select pg_reload_conf() ?
Which I execute both and they don't work either.
On Thu, Feb 28, 2013 at 12:43 PM, Chris wrote:
>
>
> On Feb 28, 2013, at 19:01, Anson Abraham wrote:
>
> *Note when I chan
db1 and db4 are 2 separate machines. no other instances of PG running on
the box, doing a pg_ctl reload did nothing as well.
Also looking @ all proecsses running, only PG instance on the box.
On Thu, Feb 28, 2013 at 2:27 PM, Adrian Klaver wrote:
> On 02/28/2013 08:19 AM, Anson Abraham wr
estination
to stderr doesn't work, however syslog does. By that i assumed then that
it must've been a perms issue, but doesn't look to be the case. Heck i
even put the file and folder as chmod 777 and still nothing.
On Thu, Feb 28, 2013 at 3:16 PM, Adrian Klaver wrote:
> On 02
I'm on Debian Wheezy running postgres 9.3
both boxes are identical.
I see in log file on slaves:
LOG: could not receive data from client: Connection reset by peer
OpenSSL is the same version on master and slaves. The libssl is also too.
I set ssl_renegotiation=0. So not sure why i'm seeing
issue. The one difference between the two slaves, the slave w/ the
message is a VM. But other master dbs i have w/ slaves (that are VMs) and
have no issues. So it's kind of odd, that this message occurs.
On Mon, Oct 21, 2013 at 6:50 AM, Albe Laurenz wrote:
> Anson Abraham wrote:
> > I
11 matches
Mail list logo
