r
performance hits because of it.
That said, the documentation here says FLOAT4 is an alias for REAL, so
it's somewhat nonintuitive for FLOAT4 to be so much slower than FLOAT8,
which is an alias for DOUBLE PRECISION.
http://www.postgresql.org/docs/9.3/static/datatype.html
Not sure
er ambitious, potential replacement.
--
Shaun Thomas
OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to
this email
well. Could we possibly extend that to UPDATE and DELETE syntax too?
--
Shaun Thomas
OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak6.com/email_disclaimer/ for term
nt gets my vote. ;) But then again, Oracle also created
VARCHAR2 and told everyone to start using that, just in case they ever
modified VARCHAR to be SQL compliant. Thankfully we have you guys, so PG
won't go down a similar route.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suit
what synchronous replication does in PG 9.1+?
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to
anyone
jumping on this before 9.4 or 9.5 unless someone sponsors the feature.
Automatic re-sync would (within available WALs) be an awesome feature,
though...
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
31
quot; mechanism yet.
Even if this isn't necessarily true, it's the safest approach IMO.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak6.com/em
work without any default naming scheme, and only incurs a
read on the file-handle.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak6.com/email_disclaimer/
seems to be some kind of
horrible flaw in the Linux kernel when it comes to properly handling
NUMA on large memory systems.
What does this say:
numactl --hardware
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
than Joe Blow's
Pentium 4 in his basement. Yet it's the latter case that's optimized for.
Servers are getting shafted in a lot of cases, and it's actually
starting to make me angry.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chica
ze, though. These last few months have been really frustrating
thanks to this and other odd kernel-related issues. We've reached an
equilibrium where the occasional waste of 20GB of RAM doesn't completely
cripple the system, but this thread kinda struck a sore point. :)
--
Shaun Thomas
Options
o increase this.
Admittedly it's a gross hack, but it works. :)
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak6.com/email_disclaimer/ for terms and conditi
process, or anything else. It's just... free. In the middle of the
day, where 800 PG threads are pulling 7000TPS on average. Based on that
scenario, I'd like to think it would cache pretty aggressively, but
instead, it's just leaving 14GB around to do absolutely nothing.
I
emory allocation to an
anonymous block, so could we simultaneously open up a DMA relationship?
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See http://www.peak
xargs command. Then you can apply the constraints, keys, and
indexes later by doing a schema-only parallel pg_restore.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
stho...@optionshouse.com
__
See
On 11/02/2012 12:31 PM, Simon Riggs wrote:
If people want full two phase commit, that option exists also.
I was about to say... isn't that what savepoints are for?
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
stho...@optionshous
ably act as a read
slave. That's currently impossible because async replication is too
slow, and sync is too fragile for reasons stated above.
Am I totally off-base, here? I was shocked when I actually read the
documentation on how sync rep worked, and saw that no servers would
fun
l listen when operating only on one device,
but at least it still works. I'm pretty sure nobody would use RAID-1 if
its failure mode was: block writes until someone installs a replacement
disk.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-44
will have the primary hang for ten seconds between
monitor checks and service reloads.
I'm just saying I considered it briefly during testing the last few
days, but there's no way I can make a business case for it. PG sync rep
is a great step forward, but it's not for us. Yet.
Well, crap. It's subtle distinctions like this I wish I'd noticed
before. Doesn't really affect our plans, it just makes sync rep even
less viable for our use case. Thanks for the correction! :)
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL
ow a warning for every
sync-required commit so long as it's in "degraded" mode. Those alone are
very small changes that don't really harm the intent of sync commit.
That's basically what a RAID-1 does, and people have been fine with that
for decades.
--
Shaun Thomas
ly ones avoiding it for exactly that reason. Our queue discards
messages it can't fulfil within ten seconds and then throws an error for
each one. We need to decouple the secondary as quickly as possible if it
becomes unresponsive, and there's really no way to do that without
something in
ver that patch I linked to originally to make
suitable adaptations. I know I talk about how relatively handy DRBD is,
but it's also a gigantic PITA since it has to exist underneath the
actual filesystem. :)
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL
he WAL
formats were compatible, the total upgrade time would only be restricted to how
long it took to replay the WAL files in the new database. Does the current
format of the WAL files make this possible? If not, is such an option for the
future?
Thanks in advance.
--
Shaun Thomas
Database Ad
24 matches
Mail list logo