Re: SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ? - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Re: SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ?
Date
Msg-id e08cc0400810120554q38ef1769wf41c7ddb3d28dccf@mail.gmail.com
Whole thread Raw
In response to SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ?  (Grzegorz Jaskiewicz <gj@pointblue.com.pl>)
Responses Re: SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ?
List pgsql-hackers
2008/10/12 Grzegorz Jaskiewicz <gj@pointblue.com.pl>:
> so I wonder, quite few times ppl asked me about my-word database TOP %
> PERCENT (and I guess ms-word db has it too).
> Now that postgres has limit(subselect) - postgresql can do the same thing.
> But, using a count(*) in subselects isn't very efficient. The backend gets
> information from limit X, so I figure it shouldn't be a very big deal to add
> LIMIT %d PERCENT , and pass it on as percentage, instead of just number of
> rows.
> I can give it a go and try to implement it myself, but wanted to ask here
> first for opinion on syntax (I have no idea what would be right syntax by
> sql standards), and how keen would you guys be on accepting such patch.
>
> thanks.
>
>

I'm afraid you will not succeed it because PostgreSQL doesn't know how
many rows are totally returned until it returns the last row, which is
as ineficient as count(*) as you point out.

Regards,


-- 
Hitoshi Harada


pgsql-hackers by date:

Previous
From: Grzegorz Jaskiewicz
Date:
Subject: SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ?
Next
From: Grzegorz Jaskiewicz
Date:
Subject: Re: SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ?