Re: [BUGS] [GENERAL] Error Starting Back END

2006-06-10 Thread Tom Lane
"Rojas, Fernando \(CIAT\)" <[EMAIL PROTECTED]> writes: > But when I locale - a the result is: > ... > en_US.utf8 > ... You probably need to spell it exactly like that, not "en_US.UTF-8". No, I don't have any idea why it worked before, if you're using the exact same OS release ... maybe you're miss

Re: [BUGS] BUG #2474: cp: cannot access ~/archivedir/00000001.history

2006-06-10 Thread Tom Lane
"Francisco Calm" <[EMAIL PROTECTED]> writes: > cp: cannot access /tempfdas/db/postgres/archivedir/0001.history This is not a bug. Note the point in the documentation that the restore command *will* be asked for files that don't exist in the archive. regards, tom lane

Re: [BUGS] BUG #2475: Row limit problem

2006-06-10 Thread Tom Lane
"Sebastiaan van Erk" <[EMAIL PROTECTED]> writes: > This shows the ENORMOUS different time it takes for the two queries even > though they both have the limit set. So? They're not the same query. (In particular, the row limit in the protocol only says how many rows to deliver in the first batch.

Re: [BUGS] BUG #2465: Installation

2006-06-10 Thread pat hayes
Jim, Thank you for all your help. From: "Jim C. Nasby" <[EMAIL PROTECTED]> To: pat hayes <[EMAIL PROTECTED]> CC: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #2465: Installation Date: Thu, 8 Jun 2006 17:02:28 -0500 See \? in psql. In particular, \d. Note that a plain '\d' won't show yo

[BUGS] BUG #2475: Row limit problem

2006-06-10 Thread Sebastiaan van Erk
The following bug has been logged online: Bug reference: 2475 Logged by: Sebastiaan van Erk Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: Windows XP Description:Row limit problem Details: When using the "raw" protocol (such as JDBC use

[BUGS] BUG #2474: cp: cannot access ~/archivedir/00000001.history

2006-06-10 Thread Francisco Calm
The following bug has been logged online: Bug reference: 2474 Logged by: Francisco Calm Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: Solaris 5.9 Description:cp: cannot access ~/archivedir/0001.history Details: I thought the histor

[BUGS] BUG #2473: Failed to open RunAs Service

2006-06-10 Thread Chris Achilli
The following bug has been logged online: Bug reference: 2473 Logged by: Chris Achilli Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Windows 2000 Server Description:Failed to open RunAs Service Details: hello, i seem to be getting an er

[BUGS] Error Starting Back END

2006-06-10 Thread Rojas, Fernando \(CIAT\)
HELLO: I have now an error similar to one posted under the subject: We had format the DISK and reinstall the SO (Red Hat Linux 8.0 3.2-7); we don't have a pg_dumpall file of support; but we have The copy of the data file that was running ok under (PG-8.0.7). We reinstall P.G 8.0.7 and try to st

Re: [BUGS] Fwd: Bug#372115: Last security update of postgresql-contrib breaks database replication with DBMirror.pl

2006-06-10 Thread Tom Lane
Martin Pitt <[EMAIL PROTECTED]> writes: > Does anyone know DBMirror.pl? The proposed fix seems wrong since it > just reverts the behavior to the old quote escaping style. I don't know it, but the function being complained of seems exactly the sort of ad-hoc escaping logic that the security update

Re: [BUGS] Fwd: Bug#372115: Last security update of postgresql-contrib

2006-06-10 Thread Bruce Momjian
Martin Pitt wrote: -- Start of PGP signed section. > Hi PostgreSQL gurus, > > we recently received this bug report after we upgraded Debian's stable > release to the equivalent of 7.4.13 (with the fixes for quote > escaping). > > Does anyone know DBMirror.pl? The proposed fix seems wrong since it

[BUGS] Fwd: Bug#372115: Last security update of postgresql-contrib breaks database replication with DBMirror.pl

2006-06-10 Thread Martin Pitt
Hi PostgreSQL gurus, we recently received this bug report after we upgraded Debian's stable release to the equivalent of 7.4.13 (with the fixes for quote escaping). Does anyone know DBMirror.pl? The proposed fix seems wrong since it just reverts the behavior to the old quote escaping style. Than