The following bug has been logged on the website:
Bug reference: 6318
Logged by: Laurenz Albe
Email address: laurenz.a...@wien.gv.at
PostgreSQL version: 9.1.1
Operating system: Linux (RHEL 3)
Description:
How to reproduce:
postgres=# CREATE DATABASE dumpme;
postgres=
Hello Craig,
it seems as if there were illegal chars in the originally dumped database,
so the dump/restore problem might be due to this. At the moment we are doing
further investigation on this issue.
But the problem regarding message output from the client applications still
persists. We
The following bug has been logged on the website:
Bug reference: 6317
Logged by: hua ming fei
Email address: h...@alkheme.com
PostgreSQL version: 9.0.1
Operating system: Centos 5.5
Description:
use pg_dump when didn't close the application , weird things occured . th
[Moving back on-list. Tom generously offered to look at the server in
question, since it seemed likely that a testcase would be difficult or
impossible to reproduce in this case]
On Fri, Dec 2, 2011 at 12:07 AM, Tom Lane wrote:
>
> Well, poking around in the process at the moment of SIGBUS, I fin
On Thursday, December 1, 2011, Tom Lane wrote:
> d.reri...@healthcareoss.com writes:
> > Simply set a varchar field in your db to the following string:
> > !"#$%'()*+,-/:;=?@[\]^_`{|}~&<>
>
> > I know, I know, who would do this, right? Well, its for a certification.
> > The like command works
laurenz.a...@wien.gv.at writes:
> dumpme=# CREATE LANGUAGE mylang HANDLER plpgsql_call_handler INLINE
> plpgsql_inline_handler VALIDATOR plpgsql_validator;
I don't think this is a particularly interesting use-case. The reason
it doesn't work for you is that it's depending on support functions
tha
