Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)
Дата
Msg-id 513E18D1.1060908@agliodbs.com
обсуждение исходный текст
Ответ на Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> Having said that, I'd still be inclined to try to set the remote's
> timezone GUC just so that error messages coming back from the remote
> don't reflect a randomly different timezone, which was the basic issue
> in the buildfarm failures we saw yesterday.  OTOH, there is no guarantee
> at all that the remote has the same timezone database we do, so it may
> not know the zone or may think it has different DST rules than we think;
> so it's not clear how far we can get with that.  Maybe we should just
> set the remote session's timezone to GMT always.

Yeah, that seems the safest choice.  What are the potential drawbacks,
if any?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



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

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]