Re: preserving forensic information when we freeze
От | Robert Haas |
---|---|
Тема | Re: preserving forensic information when we freeze |
Дата | |
Msg-id | CA+TgmoZHxHkj=GAuW_Jqop2JCMSv+0b96MzyEJ5UEVKngnqVGw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: preserving forensic information when we freeze (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Список | pgsql-hackers |
On Fri, Dec 20, 2013 at 2:17 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Robert Haas escribió: >> On Fri, Dec 20, 2013 at 1:41 PM, Alvaro Herrera >> <alvherre@2ndquadrant.com> wrote: > >> > I assume without checking that passing reloid/ctid would allow this to >> > work for tuples in a RETURNING clause; and if we ever have an OLD >> > reference for the RETURNING clause of an UPDATE, that it would work >> > there, too, showing the post-update status of the updated tuple. >> >> I don't understand what you're saying here. Are you saying that >> reloid/ctid is a better approach, a worse approach, or just a >> different approach? > > That probably wasn't worded very well. I am just saying that whatever > approach we end up with, it would be nice that it worked somehow with > RETURNING clauses. Hmm. It's not evident to me why that particular case would be any different than anything else, but that might be my ignorance showing. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: