From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | pierre(at)desertmoon(dot)com |
Cc: | herouth(at)oumail(dot)openu(dot)ac(dot)il, pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] MINUS and slow 'not in' |
Date: | 1998-11-24 16:07:06 |
Message-ID: | m0ziKza-000EBbC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
> Yeah I've got 6.4. I tried:
>
> set query_limit to 2000;
>
> and got:
>
> ERROR: parser: parse error at or near "2000"
>
> Ideas?
I think you must use '2000' instead.
Anyway, the "set query_limit" will disappear again in v6.5
(at least) because it potentially can break rewrite rule
system semantics.
Instead you might want to use the LIMIT/OFFSET patch I've
created in the v6.4 feature patch. This is what will be in
v6.5. I'll take a look how I can put it onto the server and
drop a note here after.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-11-24 16:08:42 | Re: [HACKERS] pg_dump - segfault with -z option |
Previous Message | Tom Lane | 1998-11-24 15:55:43 | Re: [HACKERS] More on 6.4 on DEC Alpha + Digital Unix 4.0d + DEC C compiler |
From | Date | Subject | |
---|---|---|---|
Next Message | dbms dbms | 1998-11-25 01:20:36 | Question about schema |
Previous Message | Jan Wieck | 1998-11-24 15:50:11 | Re: [HACKERS] Re: [SQL] cursor and update + view |