? Some
require explicit configurastion of that.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
be straight
forward to do so.-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
between
the not working /etc/postgresql/9.3/ snd the working /etc/postgresql/9.4/
is only things like 9.3 vs 9.4 in path names, the port number and the
addition in 9.4 of dynamic_shared_memory_type = mmap.
Whatever caused this is not in the config files.
-JimC
--
James Cloos cl...@jhcloos.com
| 508
The 9.3 vs 9.4 in sourcefile is the only difference between the two
clusters on that box.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
AK == Adrian Klaver adrian.kla...@aklaver.com writes:
AK So from the command line on the non-UTC machine what does the below show:
AK ~date
It is the same machine, just the old 9.3 cluster vs the new 9.4 cluster.
date returns: Mon Jun 15 19:37:14 UTC 2015
-JimC
--
James Cloos cl
box.
OE You can reconfigure the timezone for the machine:
OE sudo dpkg-reconfigure tzdata
And /etc/localtime is a copy of /usr/share/zoneinfo/Zulu.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
how do I convince it always to use utc?
(I did that test w/ ~/.psqlrc moved out of the way, but it does nothing
related to tz.)
Thanks.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
but around for a while in case there
are any other queries which might explain the differences.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
.
It wasn't the microsecond difference I asked about, it was the 6 hour
difference.
The original, ancient code I used needed to return integer seconds. And
it always gave answers consistant with date +%s.
What I haven't determined is why converting back is off by 21600 seconds.
-JimC
--
James
in reltime's coffin.
now() - to_timestamp(1427999266) worked correctly, but that is not
unexpected given to_timestamp's definition.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
DGJ == David G Johnston david.g.johns...@gmail.com writes:
DGJ ​What timezone is your server set to - and/or the client requesting the
DGJ calculation?
Everything is in UTC.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list
something obvious?
Also, is there any way to get the equiv of date +%s%N as a numeric or a
double precision?
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription
line was the
only recomendation I could find.
SF The only thing I'd say about this is that you *really* want to use
SF timestamptz in PG for storing timestamps.
I normally do, but this table hasn't changed in years. Maybe 7.4 or so
was current when it started.
Thanks!
-JimC
--
James Cloos cl
:
SELECT REGEXP_REPLACE(LOWER('300 North 126th Street'),'(\d)(st|nd|rd|th)',
'\1', 'g');
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
exists. The printf format flag is %a
for miniscule and %A for majuscule.
The result of 1./3. is 0xa.aabp-5.
This site has some info and a conversion demo:
http://gregstoll.dyndns.org/~gregstoll/floattohex/
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
queries in psql.
Incidently, this is a prime example of where the hexidecimal format
for floats would benefit pg, as it makes the text format for floats
just as suitable for round-tripping as the binary format.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
--
Sent via
which works more like %.7f.
(The wire format for floats is the same as they are stored, not a text
representation thereof.)
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
the specify
real UTC-based time or POSIX time (Currently there is a
23-second difference between the two.)
--
James Cloos [EMAIL PROTECTED] OpenPGP: 0xED7DAEA6
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please
Does anyone provide binary rpms for rh-7.3 for recent version of pgsql?
(My (aging) rh73 box is too small to compile it.)
I need to change the setup on that box to mirror a db from another via
slony. The master is at 8.0.x. In case an rh73 compatable rpm is not
available, will slony work ok
19 matches
Mail list logo