Itai Zukerman <[EMAIL PROTECTED]> writes:
>> Never leave out the "unimportant" stuff --- that's usually where you
>> went wrong ;-)
> OK, I've attached below the SQL I use to generate stuff and an
> interactive session with the "explain" etc.
Ah. Your problem is you need to mark sig_in() as IMMU
> Ah. Your problem is you need to mark sig_in() as IMMUTABLE, or at
> least [...]
That was it! Thanks!
For your enjoyment:
test=# select count(*) from x;
count
20
(1 row)
test=# explain analyze select * from x where y ~>= sig_in('{1,2,3,4,5}'::int4[]);
On Wed, 26 Feb 2003, Grignon Etienne wrote:
>
> test=# SELECT createuser('toto', true, true, true);
> NOTICE: Begin Of Update Permissions
> NOTICE: End Of Update Permissions
> NOTICE: TRIGGER
> createuser
>
> 0
> (1 row)
> test=#
>
>
> My problem is that the trigger for
Hi folks,
I've just finished writing up a bit on analyze.
http://www.freebsddiary.org/postgresql-analyze.php
It's not so much an explanation of the command as it is a series of
examples which show a query evolving from a 4 second monster to a 14
ms speed daemon.
Corrections, comments, etc app
That's exactly what I don't want to do.
I've got *very* limited HDD space for the amount of information I need to
copy out. The place to where the CSV file is would be output is NTFS and
from the Postgres documentation, it states that I should not put the table
oid files there and link in order t
