Re: [HACKERS] UPDATE of partition key
От | Amit Kapila |
---|---|
Тема | Re: [HACKERS] UPDATE of partition key |
Дата | |
Msg-id | CAA4eK1JWOhDP3eKmXttJJ1pK3UYAqLxPFnctSvzZz1n_DNQzWA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] UPDATE of partition key (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: [HACKERS] UPDATE of partition key
|
Список | pgsql-hackers |
On Wed, May 24, 2017 at 8:14 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: > On Wed, May 24, 2017 at 2:47 PM, Amit Khandekar <amitdkhan.pg@gmail.com> wrote: >> >> By now, majority of the opinions have shown that they do not favour >> two triggers getting fired on a single update. Amit, do you consider >> option 2 as a valid option ? >> > > Sounds sensible to me. > >> That is, fire only UPDATE triggers. BR on >> source partition, and AR on destination partition. Do you agree that >> firing BR update trigger is essential since it can modify the row and >> even prevent the update from happening ? >> > > Agreed. > > Apart from above, there is one open issue [1] > Forget to mention the link, doing it now. [1] - https://www.postgresql.org/message-id/CAA4eK1KEZQ%2BCyXbBzfn1jFHoEfa_OemDLhLyy7xfD1QUZLo1DQ%40mail.gmail.com -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: