Re: Prevent application log pollution with notice messages - Mailing list pgsql-general

From Andrus
Subject Re: Prevent application log pollution with notice messages
Date
Msg-id djkrnr$1f1s$2@news.hub.org
Whole thread Raw
In response to Re: Prevent application log pollution with notice messages  ("Magnus Hagander" <mha@sollentuna.net>)
Responses Re: Prevent application log pollution with notice messages
List pgsql-general
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.



pgsql-general by date:

Previous
From: David Pradier
Date:
Subject: Re: Anyone know of a Schema Comparer
Next
From: "Andrus"
Date:
Subject: Re: FoxPro in WINE to Postgresql on LINUX?