On Fri, 2002-05-31 at 22:28, Sam Liddicott wrote:
> And when I do drop a table CPU usage goes to 99% on one CPU.
When did you last do a vacuum? If you are adding and dropping temporary
tables a lot, perhaps you should vacuum pg_class and pg_attribute often
as well.
Regards,
Yes, this is certainly our error message:
pg_exec() query failed: pqReadData() -- read() failed: errno=0 No error
Of course, the "0 No error" is odd. I think that just means that read()
itself didn't set errno for the failure.
You are clearly base64 encoding the storage info, meaning
Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > See the following session examples using the form given in the documentation.
>'select timestamp(now());' fails similarly.
>
> I'm afraid you've got bit by our continuing pursuit of SQL standard
> compliance. The 7.2 release notes do point out:
>
Attached patch applied. Let me know if this is incorrect.
---
Rob Butler wrote:
> Hello all,
>
> Simple "bug"
>
> Win 32 builds do not have PQescapeString or PQescapeBytea declared in the
> libpqdll.def file. This caus
