[BUGS] BUG #6624: Tab completion of identifier containing single backslash triggers warnings

2012-05-02 Thread stuart
The following bug has been logged on the website: Bug reference: 6624 Logged by: Stuart Bishop Email address: stu...@stuartbishop.net PostgreSQL version: 9.1.3 Operating system: Ununtu Description: psql tab completion can emit WARNING messages if

Re: [BUGS] Errors on CREATE TABLE IF NOT EXISTS

2012-05-02 Thread Matteo Beccati
Hi Alvaro, On 01/05/2012 21:36, Alvaro Herrera wrote: The question you were asking has already been answered, but I think it's worth pointing out that a partitioned-insert trigger that has to check whether the partition exist beforehand is a lot slower than one that doesn't have to. Our usual

Re: [BUGS] BUG #6624: Tab completion of identifier containing single backslash triggers warnings

2012-05-02 Thread Bruce Momjian
On Wed, May 02, 2012 at 12:59:58PM +, stu...@stuartbishop.net wrote: The following bug has been logged on the website: Bug reference: 6624 Logged by: Stuart Bishop Email address: stu...@stuartbishop.net PostgreSQL version: 9.1.3 Operating system: Ununtu

Re: [BUGS] BUG #6624: Tab completion of identifier containing single backslash triggers warnings

2012-05-02 Thread Josh Kupershmidt
On Wed, May 2, 2012 at 11:21 AM, Bruce Momjian br...@momjian.us wrote: On Wed, May 02, 2012 at 12:59:58PM +, stu...@stuartbishop.net wrote: # CREATE SEQUENCE \foo; CREATE SEQUENCE # \ds \ I am unable to reproduce this failure on my copy of 9.1.3.  Have you perhaps changed any server

[BUGS] pg_dump: aborting because of server version mismatch

2012-05-02 Thread Mitesh Shah
Hi, I am trying to create a daily backup cron script but it fails with an error as below: Any pointers to resolve this will be greatly appreciated. Thanks, Mitesh Shah mitesh.s...@stripes39.com *(1) Error:* bash-3.2$ sh pg_backup_rotated_orig.sh Making backup directory in

Re: [BUGS] pg_dump: aborting because of server version mismatch

2012-05-02 Thread Kevin Grittner
Mitesh Shah mitesh.s...@stripes39.com wrote: *pg_dump: server version: 9.1.2; pg_dump version: 9.0.5* *pg_dump: aborting because of server version mismatch* This is not a bug. Use a version of pg_dump which is at least as new as the server. The older version of pg_dump is unlikely to be

Re: [BUGS] BUG #6624: Tab completion of identifier containing single backslash triggers warnings

2012-05-02 Thread Tom Lane
Josh Kupershmidt schmi...@gmail.com writes: On Wed, May 2, 2012 at 11:21 AM, Bruce Momjian br...@momjian.us wrote: On Wed, May 02, 2012 at 12:59:58PM +, stu...@stuartbishop.net wrote: # CREATE SEQUENCE \foo; CREATE SEQUENCE # \ds \ I am unable to reproduce this failure on my copy of

[BUGS] select table indicate missing chunk number 0 for toast value 96635 in pg_toast_2619

2012-05-02 Thread leo xu
hello: i see a lot ,missing chunk number 0 for toast value 96635 in pg_toast_2619,, in background aler log.select * from iclock ,no data retrun,indicate missing chunk number 0 for toast value 96635 in pg_toast_2619. i use pg_dump table,then truncate table,then pg_dump it current

Re: [seapug] Re: [BUGS] pg_dump: aborting because of server version mismatchT

2012-05-02 Thread Robert Bernier
There used to be a switch in pg_dump that would disable the version, you can even see that's in the man page. However, it is not reccommended and the most recent versions have fully deprecated the switch. Technically speaking that means that you can even use an older version of pg_dump and it

Re: [BUGS] select table indicate missing chunk number 0 for toast value 96635 in pg_toast_2619

2012-05-02 Thread Tom Lane
leo xu leoxu8...@gmail.com writes: i see a lot ,missing chunk number 0 for toast value 96635 in pg_toast_2619,, in background aler log.select * from iclock ,no data retrun,indicate missing chunk number 0 for toast value 96635 in pg_toast_2619. There is a known bug that can cause that

Re: [BUGS] BUG #6624: Tab completion of identifier containing single backslash triggers warnings

2012-05-02 Thread Stuart Bishop
On Thu, May 3, 2012 at 5:29 AM, Tom Lane t...@sss.pgh.pa.us wrote: I'm inclined to think that if we got this far without complaint, there's not a lot of point in writing new string-escaping support to solve what is now a legacy problem. I'm fine with that - I wasn't even sure if I should