Re: [HACKERS] What about LIMIT in SELECT ?
От | jwieck@debis.com (Jan Wieck) |
---|---|
Тема | Re: [HACKERS] What about LIMIT in SELECT ? |
Дата | |
Msg-id | m0zVfUW-000EBPC@orion.SAPserv.Hamburg.dsh.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] What about LIMIT in SELECT ? (Bruce Momjian <maillist@candle.pha.pa.us>) |
Ответы |
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 -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #
В списке pgsql-hackers по дате отправления: