Search Postgresql Archives

Re: Prevent application log pollution with notice messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Magnus,

thank you.  How about the main problem:

I have two commands like

CREATE TEMP TABLE tasutud1 (dokumnr INTEGER PRIMARY KEY, tasutud NUMERIC(1))
  ON COMMIT DROP;

in my transaction.

This command causes NOTICE message written to the log file.
There a number of transactions per second. So Postgres writes number notice 
messages in every second.

I don't see any reason for writing notice messages in this case. Small ON 
COMMIT DROP table will never written to disk, it exists only during 
transaction. It is not reasonable to write information about Postgres 
internal temporary memory structures to log.

Can you apply a patch which disables
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index messages at 
all or at least for temporary tables, please ?

Andrus. 



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux