eprecation notice.
I don't know how many (how few?) add pg_legacytimestamp to USE when
merging postgresql. But it is still available as of 9.6 and also
with their live build of git://git.postgresql.org/git/postgresql.git.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
S
ceil(3), Down as floor(3).)
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ns of glibc where doing certain math on double is
faster than doing it on float, depending on how things are compiled.
Maybe this is one of them?
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
useful
for some. And RC4, perhaps, also should be !ed.
And if anyone wants Kerberos tls-authentication, one could add
KRB5-DES-CBC3-SHA, but that is ssl3-only.
Once salsa20-poly1305 lands in openssl, that should be added to the
start of the list.
-JimC
--
James Cloos OpenPGP: 1
hexidecimal notation for floats 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 OpenPGP: 1024D/E
note about adding explicit mention to the docs was expressly
because it is not otherwise obvious whether indices should use lower()
or upper().
I'll ask on one of the unicode lists whether there are any locales where
a case-insensitive match should be different than a case-preserving match
of
R(column) to benefit ILIKE?
Perhaps the parser could read the former as the latter?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
quire significant surgery.
Is there any way to specify the index such that the ILIKE query will use
said index?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
mb table has several indices, including separate ones on name and ownerid.
(not my design, btw. And I really do need to re-write the middleware)
Whether it is strcoll(3) (even though LC_COLLATE is explicitly C) or
LIKE, it does make a significant difference for those two apps.
-JimC
now sets LC_CTYPE. Would that explain why lc_ctype
changed between the two clusters?
Is there any way to alter a db's lc_ctype w/o dumping and restoring? I
want to preserve some of the changes made since I copied the 9.1 cluster.
Alter database reports that lc_ctype cannot be changed.
-Jim
Its a Gentoo box; both were build from their ebuilds, with the same gcc,
flags, etc.
PE> Compare the output of pg_config --configure from both installations.
The only differences are 9.1 vs 9.2 in the paths.
Thanks,
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via
>>>>> "AF" == Andres Freund writes:
AF> Is it possible that you compiled with assertions enabled? That would
roughly
AF> fit that magnitude. SHOW debug_assertions; Should show you whether it was
AF> enabled.
Thanks, but SHOW debug_assertions r
at the plans are the same suggests that isn't
the problem, yes?
I think I recall mention from a previous beta (but goog isn't helping me
confirm) that there is some extra debugging or such enabled in the betas.
If so, and if turning that off would provide a better comparison, where
in the
only writing 8k blocks then there is probably little hope of
making efficient use of flash.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
sd for pg_xlog and the journals for the other
filesystems, but they cost too much.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ould such a patch for master be rejected?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
that the float timestamps were archaic; that avoids any
need of %A for timestamps.
That said, the possiblity of hex i/o format for the float datatypes
would be welcome.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
>>>>> "JD" == Jeff Davis writes:
JD> 2. Fix the input/output functions in a special mode for dump/reload,
JD>to make them true inverses.
That can be done by supporting the %A printf(3)/scanf(3) format.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DA
ding git
describe's dirty designation is important when using it in that
fashion. But it helps to be able to run git add --all cleanly.
I understand that other git users have similar experience.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (
re
cvsup's working files and the mirror of the repo.)
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
tamps are technically ambiguous as to whether 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)--
21 matches
Mail list logo
