Re: Getting sorted data from foreign server for merge join

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: Getting sorted data from foreign server for merge join
Дата
Msg-id CAMsr+YGgASgk1wU6v92A=qw30Yb84yJk2kkT2aAt0GGS9jAmeQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Getting sorted data from foreign server for merge join  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Список pgsql-hackers
On 16 November 2015 at 17:47, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> wrote:

collations arising from a foreign table's var are considered to be safer (FDW_COLLATE_SAFE) to push down to the foreign server , since they are either local default collation or are assumed to be same on foreign and local server as per user declaration. The onus of making that sure is on the user who declares particular collation for a foreign table var. As said upthread, different glibc implementations can cause collation ordering mismatch, this patch will be susceptible to the same problem as master/standby problem.


Yeah. It's less bad than the related problems we already have:

* Upgrading glibc can cause your indexes to no longer match your local collations
* Different glibc versions on master and replica(s) can have the same effect

I don't see a problem with adding another way this same issue can be expressed, since there's no sane way to fix it _properly_ without either versioned collations in glibc or bringing collation onboard into Pg.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Proposal: "Causal reads" mode for load balancing reads without stale data
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Proposal: "Causal reads" mode for load balancing reads without stale data