Re: [HACKERS] What about LIMIT in SELECT ?
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] What about LIMIT in SELECT ? |
Дата | |
Msg-id | 199810210609.CAA27774@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] What about LIMIT in SELECT ? (jwieck@debis.com (Jan Wieck)) |
Ответы |
Re: [HACKERS] What about LIMIT in SELECT ?
|
Список | pgsql-hackers |
> > > > > > > > > > I agree. Another good thing is that the LIMIT thing will not require a > > > > dump/reload, so it is a good candidate for a minor release. > > > > > > That's wrong, sorry. > > > > > > The limit thing as I implemented it adds 2 new variables to > > > the Query structure. Rewrite rules are stored as querytrees > > > and in the existing pg_rewrite entries that would be missing. > > > > Oh, sorry. I forgot. That could be tough. > > But it wouldn't hurt to add them now to have them in > place. The required out-, read- and copyfuncs are in > my patch too. This would prevent dump/load when we > later add the real LIMIT functionality. And it does > not change anything now. > Jan, we found that I am having to require an initdb for the INET/CIDR type, so if you want stuff to change the views/rules for the limit addition post 6.4, please send them in and I will apply them. You clearly have the syntax down, so I think you should go ahead. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: