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 Content-Description: [ 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 | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(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
