pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedlog message from autovac doesn't include db name
5+ messages / 4 participants
[nested] [flat]
* log message from autovac doesn't include db name
@ 2014-09-16 00:47 gabrielle <gorthx@gmail.com>
2014-09-16 17:06 ` Re: log message from autovac doesn't include db name Jerry Sievers <gsievers19@comcast.net>
0 siblings, 1 reply; 5+ messages in thread
From: gabrielle @ 2014-09-16 00:47 UTC (permalink / raw)
To: pgsql-admin
Hello!
I'm running 9.1.11 on CentOS. I'm getting several messages like this in my
logs:
2014-09-12 01:44:25.583 PDT,,,30540,,4dbffb0c.7b5b,5,,2014-09-12 01:41:42
PDT,74/868,0,LOG,55P03,"skipping analyze of ""foo"" --- lock not
available",,,,,,
Unfortunately, I have several databases with tables named 'foo'. I was
expecting a db name in the log message; can someone explain why it's not
there?
Thanks!
gabrielle
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: log message from autovac doesn't include db name
2014-09-16 00:47 log message from autovac doesn't include db name gabrielle <gorthx@gmail.com>
@ 2014-09-16 17:06 ` Jerry Sievers <gsievers19@comcast.net>
2014-09-16 17:52 ` Re: log message from autovac doesn't include db name Matheus de Oliveira <matioli.matheus@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Jerry Sievers @ 2014-09-16 17:06 UTC (permalink / raw)
To: gabrielle <gorthx@gmail.com>; +Cc: pgsql-admin
gabrielle <gorthx@gmail.com> writes:
> Hello!
>
> I'm running 9.1.11 on CentOS. I'm getting several messages like this in my logs:
> 2014-09-12 01:44:25.583 PDT,,,30540,,4dbffb0c.7b5b,5,,2014-09-12 01:41:42 PDT,74/868,0,LOG,55P03,"skipping analyze of ""foo"" --- lock not available",,,,,,
>
> Unfortunately, I have several databases with tables named 'foo'. I was expecting a db name in the log message; can someone explain why it's not there?
Fix your log_line_prefix setting to include DB name and then HUP your server.
>
> Thanks!
>
> gabrielle
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: log message from autovac doesn't include db name
2014-09-16 00:47 log message from autovac doesn't include db name gabrielle <gorthx@gmail.com>
2014-09-16 17:06 ` Re: log message from autovac doesn't include db name Jerry Sievers <gsievers19@comcast.net>
@ 2014-09-16 17:52 ` Matheus de Oliveira <matioli.matheus@gmail.com>
2014-09-17 04:00 ` Re: log message from autovac doesn't include db name Rajesh Madiwale <rajeshmadiwale65@gmail.com>
2014-09-17 04:11 ` Re: log message from autovac doesn't include db name gabrielle <gorthx@gmail.com>
0 siblings, 2 replies; 5+ messages in thread
From: Matheus de Oliveira @ 2014-09-16 17:52 UTC (permalink / raw)
To: Jerry Sievers <gsievers19@comcast.net>; +Cc: gabrielle <gorthx@gmail.com>; pgsql-admin
On Tue, Sep 16, 2014 at 2:06 PM, Jerry Sievers <gsievers19@comcast.net>
wrote:
> gabrielle <gorthx@gmail.com> writes:
>
> > Hello!
> >
> > I'm running 9.1.11 on CentOS. I'm getting several messages like this in
> my logs:
> > 2014-09-12 01:44:25.583 PDT,,,30540,,4dbffb0c.7b5b,5,,2014-09-12
> 01:41:42 PDT,74/868,0,LOG,55P03,"skipping analyze of ""foo"" --- lock not
> available",,,,,,
> >
> > Unfortunately, I have several databases with tables named 'foo'. I was
> expecting a db name in the log message; can someone explain why it's not
> there?
>
> Fix your log_line_prefix setting to include DB name and then HUP your
> server.
humm... This looks like CVS log, so the database name would be there if it
was a backend process, independent of log_line_prefix. Although looks like
this message came from autovacuum process, and so it won't give you the
database name.
Perhaps it should have qualified as dbname.schemaname.tablename just like
"automatic vacuum" and "automatic analyze" messages do. One could do a
feature request for that.
Regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: log message from autovac doesn't include db name
2014-09-16 00:47 log message from autovac doesn't include db name gabrielle <gorthx@gmail.com>
2014-09-16 17:06 ` Re: log message from autovac doesn't include db name Jerry Sievers <gsievers19@comcast.net>
2014-09-16 17:52 ` Re: log message from autovac doesn't include db name Matheus de Oliveira <matioli.matheus@gmail.com>
@ 2014-09-17 04:00 ` Rajesh Madiwale <rajeshmadiwale65@gmail.com>
1 sibling, 0 replies; 5+ messages in thread
From: Rajesh Madiwale @ 2014-09-17 04:00 UTC (permalink / raw)
To: Matheus de Oliveira <matioli.matheus@gmail.com>; +Cc: Jerry Sievers <gsievers19@comcast.net>; gabrielle <gorthx@gmail.com>; pgsql-admin
On Tue, Sep 16, 2014 at 11:22 PM, Matheus de Oliveira <
matioli.matheus@gmail.com> wrote:
>
> On Tue, Sep 16, 2014 at 2:06 PM, Jerry Sievers <gsievers19@comcast.net>
> wrote:
>
>> gabrielle <gorthx@gmail.com> writes:
>>
>> > Hello!
>> >
>> > I'm running 9.1.11 on CentOS. I'm getting several messages like this
>> in my logs:
>> > 2014-09-12 01:44:25.583 PDT,,,30540,,4dbffb0c.7b5b,5,,2014-09-12
>> 01:41:42 PDT,74/868,0,LOG,55P03,"skipping analyze of ""foo"" --- lock not
>> available",,,,,,
>> >
>> > Unfortunately, I have several databases with tables named 'foo'. I was
>> expecting a db name in the log message; can someone explain why it's not
>> there?
>>
>> Fix your log_line_prefix setting to include DB name and then HUP your
>> server.
>
>
> humm... This looks like CVS log, so the database name would be there if it
> was a backend process, independent of log_line_prefix. Although looks like
> this message came from autovacuum process, and so it won't give you the
> database name.
>
> Perhaps it should have qualified as dbname.schemaname.tablename just like
> "automatic vacuum" and "automatic analyze" messages do. One could do a
> feature request for that.
>
>
I Suspect that your log_line_prefix was not correctly configured in
postgresql.conf.
Try to configure log_line_prefix = '%t [%p]: [%l-1] user=%u db=%d' I think
this may help you.
Regards,
Rajesh Madiwale,
www.shreeyansh.com
> Regards,
>
>
> --
> Matheus de Oliveira
> Analista de Banco de Dados
> Dextra Sistemas - MPS.Br nível F!
> www.dextra.com.br/postgres
>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: log message from autovac doesn't include db name
2014-09-16 00:47 log message from autovac doesn't include db name gabrielle <gorthx@gmail.com>
2014-09-16 17:06 ` Re: log message from autovac doesn't include db name Jerry Sievers <gsievers19@comcast.net>
2014-09-16 17:52 ` Re: log message from autovac doesn't include db name Matheus de Oliveira <matioli.matheus@gmail.com>
@ 2014-09-17 04:11 ` gabrielle <gorthx@gmail.com>
1 sibling, 0 replies; 5+ messages in thread
From: gabrielle @ 2014-09-17 04:11 UTC (permalink / raw)
To: Matheus de Oliveira <matioli.matheus@gmail.com>; +Cc: pgsql-admin@postgresql.org, Jerry Sievers <gsievers19@comcast.net>
On Sep 16, 2014 12:52 PM, "Matheus de Oliveira" <matioli.matheus@gmail.com>
wrote:
>
>
> On Tue, Sep 16, 2014 at 2:06 PM, Jerry Sievers <gsievers19@comcast.net>
wrote:
>>
>> gabrielle <gorthx@gmail.com> writes:
>>
>> > Hello!
>> >
>> > I'm running 9.1.11 on CentOS. I'm getting several messages like this
in my logs:
>> > 2014-09-12 01:44:25.583 PDT,,,30540,,4dbffb0c.7b5b,5,,2014-09-12
01:41:42 PDT,74/868,0,LOG,55P03,"skipping analyze of ""foo"" --- lock not
available",,,,,,
>> >
>> > Unfortunately, I have several databases with tables named 'foo'. I
was expecting a db name in the log message; can someone explain why it's
not there?
>>
>> Fix your log_line_prefix setting to include DB name and then HUP your
server.
>
>
> humm... This looks like CVS log, so the database name would be there if
it was a backend process, independent of log_line_prefix.
Yep, csv log - which is why I was expecting a db name :)
Although looks like this message came from autovacuum process, and so it
won't give you the database name.
>
> Perhaps it should have qualified as dbname.schemaname.tablename just like
"automatic vacuum" and "automatic analyze" messages do. One could do a
feature request for that.
Thanks! That's the info I was looking for.
gabrielle
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2014-09-17 04:11 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-09-16 00:47 log message from autovac doesn't include db name gabrielle <gorthx@gmail.com>
2014-09-16 17:06 ` Jerry Sievers <gsievers19@comcast.net>
2014-09-16 17:52 ` Matheus de Oliveira <matioli.matheus@gmail.com>
2014-09-17 04:00 ` Rajesh Madiwale <rajeshmadiwale65@gmail.com>
2014-09-17 04:11 ` gabrielle <gorthx@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox