I've found the problem with inserting pseudo-infinite values into database
tables, and can now insert the infinity-ish values OK. The problem was
actually that pg_dump was losing precision when it dumped out the old
values. The numbers were being rounded up at the 13th or so decimal place,
causing
I'm just trying out PG7.0.2, with a view to upgrading from 6.5.3, and I've
found one quirk a little troublesome. Not sure whether I'll get any
sympathy, but I shall ask anyway :).
We find it convenient to be able to store +/- infinity for float8 values
in some database tables. With Postgres 6.5.3
Hello everyone.
I am writing a tcl/pgsql based tool. It seems that postgres version is
6.5.1. My linux distro is a SuSE 6.2.
While I issue the correct
pg_result $result -clear
after each pg_exec's, I get the
hard limit on result handles reached
error after (about) 250 queri
All,
Is there a way to ask postgres how many connections currently exist, and
who is using them, etc?
Regards,
Jeff
Ian West <[EMAIL PROTECTED]> writes:
> The question I think is more can I set the default action on requiring a
> lock on a record which is in use to be fail, rather than wait. Or can I
> specify how long to wait.
OK, I see. No, there's no such facility at the moment, though it seems
like somet
