Open daskol opened 6 years ago
Really annoying behaviour! Do you plan to do something?
We will look into this..
On Tue, 17 Oct 2017 at 9:18 PM, bbrodriges notifications@github.com wrote:
Really annoying behaviour! Do you plan to do something?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseDB/mysql_fdw/issues/148#issuecomment-337274136, or mute the thread https://github.com/notifications/unsubscribe-auth/AHmqpPngPaI8dttGazWcVSI9kko7LCsfks5stNM4gaJpZM4PWgnN .
-- Ahsan Hadi Snr Director Product Development EnterpriseDB Corporation The Enterprise Postgres Company
Phone: +92-51-8358874 Mobile: +92-333-5162114
Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb
This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Option
INIT_COMMAND
does not override time zone setting for FDW. The reason is thatmysqlBeginForeignScan
procedure creates connection, runsINIT_COMMAND
and then reset timezone. It seems that it is not necessary to force setting UTC time on connection. The propable solution is just remove this and this lines.Several steps are enumerated bellow to reproduce reported behavior.
tz
in MySQL and then create FDW in PostgreSQL likeINIT_COMMAND
to you MySQL server object