Re: [HACKERS] Transactions involving multiple postgres foreign servers
От | Masahiko Sawada |
---|---|
Тема | Re: [HACKERS] Transactions involving multiple postgres foreign servers |
Дата | |
Msg-id | CAD21AoBzcqtEOz-qWE16Eq5S1f2vZ2yJ9KsCEegg3BR2Aovw_g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Transactions involving multiple postgres foreign servers (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>) |
Ответы |
Re: [HACKERS] Transactions involving multiple postgres foreign servers
|
Список | pgsql-hackers |
On Mon, Jan 30, 2017 at 12:50 PM, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> wrote: > On Sat, Jan 28, 2017 at 8:41 PM, Peter Eisentraut > <peter.eisentraut@2ndquadrant.com> wrote: >> On 1/26/17 4:49 AM, Masahiko Sawada wrote: >>> Sorry, I attached wrong version patch of pg_fdw_xact_resovler. Please >>> use attached patch. >> >> So in some other thread we are talking about renaming "xlog", because >> nobody knows what the "x" means. In the spirit of that, let's find >> better names for new functions as well. > > It's common in English (not just the database jargon) to abbreviate > "trans" by "x" [1]. xlog went a bit far by abbreviating whole > "transaction" by "x". But here "xact" means "transact", which is fine. > May be we should use 'X' instead of 'x', I don't know. Said that, I am > fine with any other name which conveys what the function does. > > [1] https://en.wikipedia.org/wiki/X > "txn" can be used for abbreviation of "Transaction", so for example pg_fdw_txn_resolver? I'm also fine to change the module and function name. Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: