Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I certainly don't see the point of the implementation as you have it
--- it adds a great deal of unnecessary infrastructure compared to just
installing a symlink at share/postgresql/timezone.
The point of my solution is
Magnus Hagander wrote:
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
This patch brings possibility to switch from default build-in timezone
to another timezone source - typically to OS timezone location.
It was discussed few weeks ago:
http://archives.postgresql.org/pgsql-hackers/2
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I certainly don't see the point of the implementation as you have it
>> --- it adds a great deal of unnecessary infrastructure compared to just
>> installing a symlink at share/postgresql/timezone.
> The point of my solution is that al
Tom Lane wrote:
Zdenek Kotala <[EMAIL PROTECTED]> writes:
This patch brings possibility to switch from default build-in timezone
to another timezone source - typically to OS timezone location.
It was discussed few weeks ago:
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00784.php
Tom Lane wrote:
> Zdenek Kotala <[EMAIL PROTECTED]> writes:
>> This patch brings possibility to switch from default build-in timezone
>> to another timezone source - typically to OS timezone location.
>
>> It was discussed few weeks ago:
>> http://archives.postgresql.org/pgsql-hackers/2007-03/msg
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> This patch brings possibility to switch from default build-in timezone
> to another timezone source - typically to OS timezone location.
> It was discussed few weeks ago:
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00784.php
AFAIR, the co
