Shelby Cain wrote:
I believe this is expected behavior the Ctrl-\ keystroke will cause a SIGQUIT
to the current process. Any program that doesn't explicitly handle SIGQUIT
will abort.
Regards,
Shelby Cain
Okay, thanks for the reply, and sorry for the noise.
Jeff
-
eg in size, so I can either upload it to
our web site or e-mail it directly to someone if anyone is interested.
Thanks,
Jeff Ross
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
The following bug has been logged online:
Bug reference: 2455
Logged by: Jeff Ross
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: OpenBSD 3.9 -current
Description:psql failing to restore a table because of a constaint
violation.
Details
Tom Lane wrote:
Jeff Ross <[EMAIL PROTECTED]> writes:
Rather than post it in the e-mail, I've put the postmaster.log at
http://www.openvistas.net/postmaster.log
I see multiple occurrences of
LOG: could not fork new process for connection: Resource temporarily
unavailable
so
Tom Lane wrote:
Michael Fuhr <[EMAIL PROTECTED]> writes:
On Fri, Jan 21, 2005 at 05:03:08PM -0700, Jeff Ross wrote:
If I put the same source code up on a ram disk, configure and compile it
the same way, all 96 tests pass.
Interesting. Is this behavior consistent? What's different
ssors with 2 GB of RAM. Operating
system is OpenBSD 3.6.
I'm a little leary of upgrading my PostgreSQL installation with those
kind of failure rates.
I'd appreciate any insight as to why so many tests would fail when run
on disk and pass when run in ram.
Th
is OpenBSD 3.6.
I'm currently running 7.3.5, which I'd love to upgrade but I'm a little
leary until I can determine what is causing this error.
Any thoughts greatly appreciated!
Jeff Ross
---(end of broadcast)---
TIP 6: Have you se
