From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: [HACKERS] TODO list updated |
Date: | 2000-01-13 01:16:15 |
Message-ID: | 000201bf5d63$c9c8f8c0$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Bruce Momjian
>
> I have updated the TODO list to mark all the items that are completed
> for 7.0.
>
> Are there any additional ones? Are there some names I have forgotten to
> attribute to items?
>
> Let me know.
>
Hmmm,who solved ????
* -spinlock stuck problem when elog(FATAL) and elog(ERROR) inside bufmgr
And I have felt that the followings are almost same.
* Allow LIMIT ability on single-table queries that have no ORDER BY to use
a matching index [limit]
* Improve LIMIT processing by using index to limit rows processed [limit]
* Have optimizer take LIMIT into account when considering index scans
[limit]
And Isn't it preferable to omit 'in ORDER BY' from
* Use indexes in ORDER BY for restrictive data sets, min(), max()
?
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-01-13 01:26:54 | Re: [HACKERS] TODO list updated |
Previous Message | Tom Lane | 2000-01-13 01:13:02 | Re: [HACKERS] FETCH without FROM/IN |