Julius Tuskenis <[EMAIL PROTECTED]> writes:
> I've noticed that statement SELECT current_timestamp AT TIME ZONE
> 'Europe/Vilnius' returns me an error:
> ERROR: time zone "Europe/Vilnius" not recognized
> SQL state: 22023
> Time zone Europe/Vilnius is the systems timezone. I checked in
> pgsql/s
Thank you for your answer.
I've noticed that statement SELECT current_timestamp AT TIME ZONE
'Europe/Vilnius' returns me an error:
ERROR: time zone "Europe/Vilnius" not recognized
SQL state: 22023
Time zone Europe/Vilnius is the systems timezone. I checked in
pgsql/share/timezone the file is in
Julius Tuskenis <[EMAIL PROTECTED]> writes:
> I have problem with postgreSQL current_timestramp. Where does it get its
> value, because it doesnt match system time. The problem appeared after
> this saturday-sunday night and is connected somehow with the daylight
> saving. Now "date" on the serv
On Mon, Mar 31, 2008 at 4:19 PM, Alexey Klyukin <[EMAIL PROTECTED]>
wrote:
> > And may be someone have such script or other ideas how to log
> long-running
> > statements in order to optimize them?
>
> I suggest you to take a look at pgFouine:
> http://pgfouine.projects.postgresql.org/
Yes, acco
Just empty strings in datconfig.
"postgres";""
"sportlog";""
"template1";""
"template0";""
"sport";""
Tommy Gildseth rašė:
How about database specific config settings?
SELECT datname, datconfig FROM pg_database;
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make chan
Vladimir Rusinov wrote:
> Hello!
>
> I need a daily list of log-running statements. I've turned on
> log_min_duraion_statement and going to write script which would daily parse
> postgresql log and mail it to me, but I have no long-running statements (and
> don't wanna do specially) and I can't se
How about database specific config settings?
SELECT datname, datconfig FROM pg_database;
--
Tommy Gildseth
Julius Tuskenis wrote:
Yes, it is undefined (#timezone = unknown) just like in other servers.
Julius
Vishal Arora rašė:
Have you checked timezone parameter in postgresql.conf file?
Yes, it is undefined (#timezone = unknown) just like in other servers.
Julius
Vishal Arora rašė:
Have you checked timezone parameter in postgresql.conf file?
- Vishal
> Date: Mon, 31 Mar 2008 13:18:41 +0300
> From
Hello!
I need a daily list of log-running statements. I've turned on
log_min_duraion_statement and going to write script which would daily parse
postgresql log and mail it to me, but I have no long-running statements (and
don't wanna do specially) and I can't see any in my log file. How does they
Have you checked timezone parameter in postgresql.conf file?
- Vishal
> Date: Mon, 31 Mar 2008 13:18:41 +0300> From: [EMAIL PROTECTED]> CC:
> pgsql-admin@postgresql.org> Subject: Re: [ADMIN] what is the origin of
> postgreSQL time> > If I use select current_timestamp AT TIME ZONE 'EEST' I
If I use select current_timestamp AT TIME ZONE 'EEST' I get good time
(EEST - I'm in Lithuania). But how do I make postgreSQL use system time
by default? The thing is we have 8 servers working and none of them is
affected by this issue. Only one refuses to switch to summer time.
Julius Tuskeni
beware of timezone dst offset. try
select current_timestamp AT TIME ZONE 'MEST'
thomas
Julius Tuskenis schrieb:
Hello,
I have problem with postgreSQL current_timestramp. Where does it get
its value, because it doesnt match system time. The problem appeared
after this saturday-sunday night an
Hello,
I have problem with postgreSQL current_timestramp. Where does it get its
value, because it doesnt match system time. The problem appeared after
this saturday-sunday night and is connected somehow with the daylight
saving. Now "date" on the server returns good value, but the SELECT
curr
On Mon, Mar 31, 2008 at 01:26:52AM -0500, Potluri Srikanth wrote:
>how can i reduce the time ?
try this:
http://pgbulkload.projects.postgresql.org/
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly paid DBA. here's my CV!" :)
http://www.depesz.com/ - blog
14 matches
Mail list logo
