Craig Longman <[EMAIL PROTECTED]> writes:
> so, i presume then that this is a problem in the database because no-one
> has sat down and made sure that all the possible combinations of
> built-in datatypes are handled for all the various built-in
> functions/operators?
No, that's not it, and that
On 17 Jun 2001 21:02:03 -0500, Ross J. Reedstrom wrote:
> On Sat, Jun 16, 2001 at 01:07:29AM -0400, Craig Longman wrote:
>
> numeric casts>
>
> Tom Lane has already addressed the 'why is it this way' question. I'll
> address your proposed work arounds.
he did. i tried looking in pg-hackers for
On Sat, Jun 16, 2001 at 01:07:29AM -0400, Craig Longman wrote:
numeric casts>
Tom Lane has already addressed the 'why is it this way' question. I'll
address your proposed work arounds.
>
> the only solution i can think of, if it is possible, is to have a script
> that the client would need to
Jie Liang <[EMAIL PROTECTED]> writes:
> I vacuumed urlinfo already.
VACUUM ANALYZE, or just VACUUM?
> urlinfo_pkey is primary key (id), urlinfo_ukey is unique key (url)
> when I:
> SELECT id FROM urlinfo WHERE url='http://*.yahoo.com';
> It seems taking me longer than before.
What does EXPLAIN
Jie Liang <[EMAIL PROTECTED]> writes:
> the original schema includes another constraint which using a user defined
> function to check whether url is validate or not.
So are you saying it was just a bug in this user-defined function?
Or is there something we need to investigate?
Jie Liang <[EMAIL PROTECTED]> writes:
> when I reload my database from pg_dumpall:
> COPY "urlinfo" FROM stdin;
> ERROR: copy: line 11419, MemoryContextAlloc: invalid request size
> 4294967271
> PQendcopy: resetting connection
Postgres version? Table schema? Input data?
Helo,
I'm using postgresql 7.1, with suse linux 7.1 on i386.
I'm programming in python and I'm going to store many, long (approx. 600
bytes) python-variables in a postgres database. There is a way to convert
python-variables into string (either binary or text) format to make them
possible to b
