Re: [HACKERS] REPLICA IDENTITY FULL
От | Craig Ringer |
---|---|
Тема | Re: [HACKERS] REPLICA IDENTITY FULL |
Дата | |
Msg-id | CAMsr+YGtPWki+=6chsLMk=yEHdNj721jzSku6_jnjNtO+dzyvw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] REPLICA IDENTITY FULL (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: [HACKERS] REPLICA IDENTITY FULL
|
Список | pgsql-hackers |
On 20 June 2017 at 09:47, Andres Freund <andres@anarazel.de> wrote: > On 2017-06-20 09:45:27 +0800, Craig Ringer wrote: >> I frequently want to be able to use REPLICA IDENTITY DEFAULT, but also >> record the whole old tuple not just keys, so they can be used in >> conflict processing etc. > > What stops you from automatically using a candidate key if available? Nothing, and that's what I do. I just think it's a bit fuzzy. Maybe I'm misunderstanding the purpose of REPLICA IDENTITY, but I read it as saying "this is the replication key for this relation". If you use REPLICA IDENTITY FULL then the replication tool goes "nah, I think I'll pick the PK instead" is that really right? It's not a major issue. -- Craig Ringer http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: