Re: [GENERAL] Strange error message when reference non-existent column foo."count"

2014-12-17 Thread Tom Lane
Patrick Krecker writes: > As expected, the following fails: > select count from foo; > ERROR: column "count" does not exist > LINE 1: select count from foo; >^ > But if I change the syntax to something I thought was equivalent: > select foo."count" from foo; > count > --- >

Re: [GENERAL] Strange error message when reference non-existent column foo."count"

2014-12-17 Thread Patrick Krecker
Sorry, I changed the email as I was writing it but I forgot to change the subject line. An appropriate subject would be 'Strange behavior when referencing non-existent column foo."count".' On Wed, Dec 17, 2014 at 2:50 PM, Patrick Krecker wrote: > > I encountered this today and it was quite surpri

[GENERAL] Strange error message when reference non-existent column foo."count"

2014-12-17 Thread Patrick Krecker
I encountered this today and it was quite surprising: select version(); version -- PostgreSQL 9.3.5 on x86_64-unknown-linux-gnu, compiled by gcc (Ubu

Re: [GENERAL] Strange error message

2006-08-02 Thread Tom Lane
"Christian Rengstl" <[EMAIL PROTECTED]> writes: > Unfortunately it's windows, but nevertheless it worked now for weeks > and suddenly the postgre user should not be able to copy anymore? Broken anti-virus software. We've seen essentially identical reports before ... regar

Re: [GENERAL] Strange error message

2006-08-02 Thread Frank Finner
Disk full or otherwise problems with the disk? I remember I saw somthing similiar some months ago and the reason was (AFAIR) something like a full partition or a partition set to readonly, or a broken mountpoint because of hardware errors. With Linux, not MSW. Regards, Frank On Wed, 02 Aug 20

Re: [GENERAL] Strange error message

2006-08-02 Thread Christian Rengstl
The thing is that the very same file was copied to the specified directory. Martijn van Oosterhout wrote on 08/02/06 9:43 am: > On Wed, Aug 02, 2006 at 09:34:25AM +0200, Christian Rengstl wrote: >> it seems as if in /pg_xlog/archive_status the respective file >> 0001002000D2.ready was

Re: [GENERAL] Strange error message

2006-08-02 Thread Christian Rengstl
Unfortunately it's windows, but nevertheless it worked now for weeks and suddenly the postgre user should not be able to copy anymore? Besides, the file was copied and then disappeared from the pg_xlog directory, nevertheless postgre kept trying to copy the very same file. "A. Kretschmer" <[EMA

Re: [GENERAL] Strange error message

2006-08-02 Thread Martijn van Oosterhout
On Wed, Aug 02, 2006 at 09:34:25AM +0200, Christian Rengstl wrote: > it seems as if in /pg_xlog/archive_status the respective file > 0001002000D2.ready was not changed to > 0001002000D2.done. Can this be done manually? About the > persmission denied error i still have absolu

Re: [GENERAL] Strange error message

2006-08-02 Thread A. Kretschmer
am 02.08.2006, um 9:27:22 +0200 mailte Christian Rengstl folgendes: > Postgre copied the file 0001002000D2 to the specified directory > and now it says it can't be copied...I really, really don't get it! My guess: Access Denied on the filesystem for the postgres-User. PS.: Windows,

Re: [GENERAL] Strange error message

2006-08-02 Thread Christian Rengstl
it seems as if in /pg_xlog/archive_status the respective file 0001002000D2.ready was not changed to 0001002000D2.done. Can this be done manually? About the persmission denied error i still have absolutely no clue! "Christian Rengstl" <[EMAIL PROTECTED]> wrote on 08/02/06

[GENERAL] Strange error message

2006-08-02 Thread Christian Rengstl
Hi everyone, can please somebody let me know what this error message is supposed to mean: ERROR: could not open relation 1663/16858/9469857: Permission denied Strange thing about it is that i do not have a relation with that name. This somehow seems to go along with this other strange error mess