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

Re: high values for client_min_messages

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: high values for client_min_messages
Date: 2005-10-13 20:58:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Patch applied.  Thanks.


Kris Jurka wrote:
> 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, skipping... ]

> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2005-10-13 21:04:47
Subject: Re: roundoff problem in time datatype
Previous:From: Bruce MomjianDate: 2005-10-13 20:53:55
Subject: Re: roundoff problem in time datatype

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