"Andrus" <[EMAIL PROTECTED]> writes:
> I don't see any reason for writing notice messages in this case.
So increase log_min_messages. (I'm not real sure why that defaults
to NOTICE, either, except perhaps habit.)
regards, tom lane
---(end of broad
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 P
> Also:
>
> They cannot be filterad out since all Postgres log entries
> have type Error, e.q.
> LOG: database system is ready message is Erorr message !
>
> Why postgres uses Error category for NOTICES ? Is'nt it
> reasonable to use Information type ?
This should be fixed in 8.0.4, and in
My appl creates temporary table with primary key which exists only during
transaction.
Each creation of such table causes Postgres to write an entry to Windows
application log file like:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"taitmata_pkey" for table "taitmata"
I have lot
