Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, I did a little research on this. It turns out that this code in
> vacuum.c:
> if (vacstmt->verbose)
> MESSAGE_LEVEL = NOTICE;
> else
> MESSAGE_LEVEL = DEBUG;
> controls whether the message comes out as a NOTICE or a DEBUG
Sure,
I have about 70 tables, each vacuum prints out something like this per
table. You'll notice it prints stuff for each index also.
postgres[23034]: [566] DEBUG: --Relation test--
postgres[23034]: [567-1] DEBUG: Pages 1: Changed 1, reaped 1, Empty 0,
New 0; Tup 3: Vac 1, Keep/VTL 0/0, Cr
Jon writes:
> I'm not using pg_ctl, I'm using postmaster directly. So, in my case I
> tried passing "-d0" to it, but it had no effect. Command line:
>
> postmaster -i -d0 -D /var/pgsql/data -c syslog=2
>
> Any ideas? I could patch the code to remove the excessive elog's in the
> vacuum com
Can you give me a few sample lines that you are seeing in the log?
> Hi,
> I'm not using pg_ctl, I'm using postmaster directly. So, in my case I
> tried passing "-d0" to it, but it had no effect. Command line:
>
> postmaster -i -d0 -D /var/pgsql/data -c syslog=2
>
> Any ideas? I could p
Hi,
I'm not using pg_ctl, I'm using postmaster directly. So, in my case I
tried passing "-d0" to it, but it had no effect. Command line:
postmaster -i -d0 -D /var/pgsql/data -c syslog=2
Any ideas? I could patch the code to remove the excessive elog's in the
vacuum command, but I'd rather
Hi,
This might sound weird, but try "
pg_ctl start -o '-d0'
Include any other options you need of course too. The point is not
having a space between the -d and the 0.
This fixes things for me when I have the default startup options
different, but need logging off for a while.
Regards and be
