inline:
On Thu, Feb 20, 2014 at 3:57 AM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
No doubt this is solution and doable but doesn't fit into my current deployment model.
Yes as mentioned earlier here is the POA - a perl function to get the timezone on both windows and linux then map them to the pg_timezone_names table to get actual names in format "Asia/Calcutta" and set this as timezone parameter in postgreSQL.conf to workaround things.
JDBC there is no issue. However if there is any clue at ODBC driver level, please let know.
The functionality of determining an IANA timezone name equivalent to the
platform's behavior is currently embedded in initdb and isn't separately
accessible. So you've got several options:
Hmm, actually was looking for exact that command which could resolve my requirement. But as you explained its not separately available.
1. Wait to do initdb until the machine is installed.
No doubt this is solution and doable but doesn't fit into my current deployment model.
2. Modify the timezone setting in postgresql.conf after the machine is
installed (although there might not be an easy way to determine what
to set it to).
Yes as mentioned earlier here is the POA - a perl function to get the timezone on both windows and linux then map them to the pg_timezone_names table to get actual names in format "Asia/Calcutta" and set this as timezone parameter in postgreSQL.conf to workaround things.
3. Leave the server timezone setting as GMT and rely on clients to select
the zone they want to work in.
JDBC there is no issue. However if there is any clue at ODBC driver level, please let know.
Regards...
