I've a question that's somehow relateted to this bug. I hope it's ok to
post it here, even if it's not a bug report.
We are planning to set up a standby system, in case our productive
database system crashes again. Replication by WAL archiving is one
possible solution. But the question is: would a
The following bug has been logged online:
Bug reference: 3652
Logged by: Robert Kleemann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: linux, solaris 10
Description:quiet / VERBOSITY=terse does not silence PKEY NOTICE
message
Details:
"Robert Kleemann" <[EMAIL PROTECTED]> writes:
> Even if quiet and verbosity terse is set, creating a table with a primary
> key will generate a NOTICE message that reports an index is being created.
Those have nothing to do with it; in fact I don't think "\set quiet" has
any effect at all... Try
Thanks Tom! That did the trick. I didn't know this could be set outside
of the configuration file.
Robert.
Those have nothing to do with it; in fact I don't think "\set quiet" has
any effect at all... Try "SET client_min_messages" instead.
regards, tom lane
-
The following bug has been logged online:
Bug reference: 3653
Logged by: Marc Munro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Linux 2.6.15.6 #4 SMP PREEMPT i686
Description:Database crash
Details:
Also occurs on 8.2.3 and 8.1.4
Th
"Marc Munro" <[EMAIL PROTECTED]> writes:
> The following script causes a db server crash:
You are using the I/O routines for the builtin "char" type, but you
have not duplicated the storage parameters for that type. The length
must be 1 not -1, and it's pass by value.
reg
