Re: [HACKERS] Alternative to LIMIT in SELECT ?

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: t-ishii(at)sra(dot)co(dot)jp
Cc: t-ishii(at)sra(dot)co(dot)jp, lockhart(at)alumni(dot)caltech(dot)edu, marc(at)fallon(dot)classyad(dot)com, eric(at)linux-hw(dot)com, scrappy(at)hub(dot)org, jeff(at)remapcorp(dot)com, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Alternative to LIMIT in SELECT ?
Date: 1998-10-14 05:12:52
Message-ID: 199810140512.BAA17725@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Applied, with one question.

> >>> I've found ExecutorLimit() (in executor/execMain.c) is useful for me
> >>> especially when issuing an ad-hock query via psql. I personally use
> >>> the function with customized set command.
> >>
> >>Looks interesting. So where are the patches? :)
> >
> >I'll post pacthes within 24 hours:-)
>
> Here it is.
> + #ifdef QUERY_LIMIT
> + static bool
> + parse_query_limit(const char *value)
> + {
> + int32 limit;
> +
> + if (value == NULL) {
> + reset_query_limit();
> + return(TRUE);
> + }

Any idea how 'value' could be null? I could not see how that would
happen. I can see how GEQO could have a NULL when you say ON, and no
value. Same with rplans.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 1998-10-14 05:53:54 Re: [HACKERS] Alternative to LIMIT in SELECT ?
Previous Message Tatsuo Ishii 1998-10-14 04:11:20 Re: [HACKERS] Alternative to LIMIT in SELECT ?