Skip site navigation (1) Skip section navigation (2)

high values for client_min_messages

From: Kris Jurka <books(at)ejurka(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Subject: high values for client_min_messages
Date: 2005-09-28 01:18:15
Message-ID: Pine.BSO.4.61.0509272003590.30956@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-patches
The patch updates the documentation to reflect the fact that higher values 
of client_min_messages (fatal + panic) are valid and also fixes a slight 
issue with how psql tried to display error messages that aren't sent to 
the client.

We often tell people to ignore errors in response to requests for things 
like "drop if exists", but there's no good way to completely hide this 
without upping client_min_messages past ERROR.  When running a file like

SET client_min_messages TO 'FATAL';

DROP TABLE doesntexist;

with "psql -f filename" you get an error prefix of 
"psql:/home/username/filename:3" even though there is no error message to 
prefix because it isn't sent to the client.

Kris Jurka

Attachment: high_client_messages.patch
Description: text/plain (2.0 KB)

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2005-09-28 02:38:50
Subject: Re: Proposed patch for sequence-renaming problems
Previous:From: Bruce MomjianDate: 2005-09-27 23:44:20
Subject: Re: Proposed patch for sequence-renaming problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group