Postgres Pro
Downloads
Home   >   mailing lists

Thread: Assign the system timezone to a variable in a function?

Assign the system timezone to a variable in a function?

From
"Steve Murphy"
Date:

I have read the docs twice; I have tried all sorts of things;

there must be some way to do this simple thing:

 

Take the result of "show timezone", and assign it to a variable

in a function.

 

murf

 

 

 

 

 

 

 

Re: Assign the system timezone to a variable in a function?

From
Merlin Moncure
Date:
On Tue, May 24, 2011 at 8:09 AM, Steve Murphy <smurphy@intorrent.com> wrote:
> I have read the docs twice; I have tried all sorts of things;
>
> there must be some way to do this simple thing:
>
>
>
> Take the result of "show timezone", and assign it to a variable
>
> in a function.

I was about to suggest querying the pg_settings table, then noticed
there was no 'timezone' record in it, which is pretty odd imo.  You
can look at the log_timezone record however, which might be correct.

merlin

Re: Assign the system timezone to a variable in a function?

From
Tom Lane
Date:
Merlin Moncure <mmoncure@gmail.com> writes:
> On Tue, May 24, 2011 at 8:09 AM, Steve Murphy <smurphy@intorrent.com> wrote:
>> Take the result of "show timezone", and assign it to a variable
>> in a function.

> I was about to suggest querying the pg_settings table, then noticed
> there was no 'timezone' record in it, which is pretty odd imo.  You
> can look at the log_timezone record however, which might be correct.

It's spelled "TimeZone" for historical reasons.  See also the
current_setting() function.

            regards, tom lane

Re: Assign the system timezone to a variable in a function?

From
Merlin Moncure
Date:
On Tue, May 24, 2011 at 8:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Merlin Moncure <mmoncure@gmail.com> writes:
>> On Tue, May 24, 2011 at 8:09 AM, Steve Murphy <smurphy@intorrent.com> wrote:
>>> Take the result of "show timezone", and assign it to a variable
>>> in a function.
>
>> I was about to suggest querying the pg_settings table, then noticed
>> there was no 'timezone' record in it, which is pretty odd imo.  You
>> can look at the log_timezone record however, which might be correct.
>
> It's spelled "TimeZone" for historical reasons.  See also the
> current_setting() function.

whoops!  I should have known... :-).  Yeah, the current_setting()
function is just a hair faster than grepping the pg_settings view for
the right answer, and so is really the better way to go anyways.  It
also is case agnostic apparently.

merlin