From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | jwieck(at)debis(dot)com |
Cc: | pierre(at)desertmoon(dot)com, herouth(at)oumail(dot)openu(dot)ac(dot)il, pgsql-sql(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org (PostgreSQL HACKERS) |
Subject: | LIMIT patch available (was: Re: [SQL] MINUS and slow 'not in') |
Date: | 1998-11-25 11:08:46 |
Message-ID: | m0zicoQ-000EBQC@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.
Done. URL is:
ftp://ftp.postgresql.org/pub/patches/v6.4-feature-patch.tar.gz
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 | The Hermit Hacker | 1998-11-25 14:12:38 | Re: [HACKERS] 6.4.x |
Previous Message | Jan Wieck | 1998-11-25 10:37:04 | Re: [HACKERS] Re: [SQL] cursor and update + view |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-11-25 15:55:33 | Re: Question about schema |
Previous Message | Jan Wieck | 1998-11-25 10:37:04 | Re: [HACKERS] Re: [SQL] cursor and update + view |