a new user aspect called MONITOR (similar
to REPLICATION)? We can grant application_name and replication details
to that.
Yeah, except I don't see doing the MONITOR thing for 9.4. We'd need a
spec for it first.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
that stddev will pay its
way, but I'm much less certain about the others.
What I really want is percentiles, but I'm pretty sure we already shot
that down. ;-)
I could use min/max -- think of performance test runs. However, I agree
that they're less valuable than stddev.
--
Josh Berkus
PostgreSQL
still
think that's the best way to go.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
complex objects type JSON?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and clarification.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. Sometimes it's an array, or an
object, or a boolean, and for those I won't call the _text version
afterwards but just use the original.
It would make more sense to extract them as JSON, check the type, and
convert.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
of the application period (Feb 15). We
can't have a repeat of last year.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
*were* minimum acceptable. Certainly they're as complete as
the original JSON docs were.
Or is this just about whitespace and line breaks?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 01/28/2014 10:56 AM, Alvaro Herrera wrote:
Josh Berkus escribió:
Or is this just about whitespace and line breaks?
If the docs are going to be rehauled, please ignore my whitespace
comments.
I'm sure you'll find plenty to criticize in my version. ;-)
--
Josh Berkus
PostgreSQL
an unpriv user access to the
WAL columns in pg_stat_replication so that I can monitor replication
delay without granting superuser permissions.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On 01/28/2014 12:10 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
For example, I would really like to GRANT an unpriv user access to the
WAL columns in pg_stat_replication so that I can monitor replication
delay without granting superuser permissions.
Just out of curiosity, why
, we'd need some easy way to
determine that the master was in a state of permanent degrade, and a
command to make it resync.
Discuss?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
depends on a timing-based feedback loop is going to be
hopeless. Saying autovac shouldn't run if load is high sounds like a
simple statement, until you actually try to implement it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
, I prefer the parameter to having differently named functions.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
activity, a lot more people would turn
it off.
Now, if you were to argue that we should have some way to monitor the
tables which autovac can never touch because of conflicts, I would agree
with you.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing
case) to cover this case, I can try to dig it out
again and clean it up...
It would be 100% more information than we currently have. How much more
difficult would it be to count completed autovacuums as well? It's
really the ratio of the two which matters ...
--
Josh Berkus
PostgreSQL Experts
On 01/23/2014 02:55 PM, Josh Berkus wrote:
On 01/23/2014 02:17 PM, Magnus Hagander wrote:
FWIW, I have a patch around somewhere that I never cleaned up properly for
submissions that simply added a counter to pg_stat_user_tables indicating
how many times vacuum had aborted on that specific
.
That would work for me, personally. I don't know how it would work for
anyone else.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
All,
pg_isready works against older versions of PostgreSQL. Does anyone know
if there's a limit to that? v3 protocol change? Something else?
Backwards compatibility ought to be in its docs, but to fix that I need
to know what version it's compatible *to*.
--
Josh Berkus
PostgreSQL Experts
requires the handyrep database user
to be a superuser.
It would be really nice to be able to GRANT/REVOKE on some of these
special system views ...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Mel,
So we have a few interested parties. What do we need to do to set up
the Collab session?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
an include_dir
postgresql.conf.d currently in the stock postgresql.conf, but it's
disabled (commented out) by default. I'd just like it enabled by
default, and to pass a suggestion to the packagers that they pick an
appropriate directory and enable it by default.
--
Josh Berkus
PostgreSQL Experts Inc.
http
be configurable
by distros, packagers and users.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, since we're about to do 9.3.3: was this patch ever committed?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
Yes, I'm also arguing that postgresql.auto.conf should go into conf.d.
I said I'd bring that up again after ALTER SYSTEM SET was committed, and
here it is.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
that line of argument. Where is auto.conf now?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
with Amazon later this week and checking how they're
handling their tenant-loadable extensions. I'd like to come up with one
solution here which covers all cloud providers.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
regimen for testing database performance on Linux kernels.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
to get out of Collab would be a
reasonable regimen for testing database performance on Linux
kernels.
... or perhaps you figure this is what would bring such issues to
the community's attention before people are bitten in production
environments?
That, too.
--
Josh Berkus
PostgreSQL
Everyone,
I am looking for one or more hackers to go to Collab with me to discuss
this. If you think that might be you, please let me know and I'll look
for funding for your travel.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql
to the processors stuff was running on, but that includes an implicit
assumption that no individual process will ever want more than one
memory bank worth of cache.
So disabling all of the NUMA optimizations is the way to go for any
workload I personally deal with.
--
Josh Berkus
PostgreSQL
to pop off the first row, and ignored the
rest. I doubt anyone else does, either.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On 01/13/2014 04:20 PM, Jim Nasby wrote:
On 1/13/14, 5:57 PM, Josh Berkus wrote:
I *really* don't want to go through all my old code to find places where
I used SELECT ... INTO just to pop off the first row, and ignored the
rest. I doubt anyone else does, either.
Do you regularly have use
On 01/13/2014 05:10 PM, Jim Nasby wrote:
On 1/13/14, 7:06 PM, Josh Berkus wrote:
Regularly? No. But I've seen it, especially as part of a does this
query return any rows? test. That's not the best way to test that, but
that doesn't stop a lot of people doing it.
Right, and I certainly
it,
replication is impossible and there's no workaround.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 01/13/2014 05:30 PM, Dave Chinner wrote:
On Mon, Jan 13, 2014 at 03:24:38PM -0800, Josh Berkus wrote:
No matter what default NUMA allocation policy we set, there will be
an application for which that behaviour is wrong. As such, we've had
tools for setting application specific NUMA policies
On 01/13/2014 05:48 PM, Andres Freund wrote:
On 2014-01-13 10:56:00 -0800, Josh Berkus wrote:
Well, it was the lack of sysctl options which takes the 2Q change from
annoyance to potential disaster. We can't ever get away from the
possibility that the Postgres use-case might be the minority
:
On Sat, Jan 11, 2014 at 07:18:02PM -0800, Josh Berkus wrote:
In other words, if we're going to have auto-degrade, the most
intelligent place for it is in
RepMgr/HandyRep/OmniPITR/pgPoolII/whatever. It's also the *easiest*
place. Anything we do *inside* Postgres is going to have a really,
really
On 01/12/2014 12:35 PM, Stephen Frost wrote:
* Josh Berkus (j...@agliodbs.com) wrote:
You don't want to handle all of those issues the same way as far as sync
rep is concerned. For example, if the standby is restaring, you
probably want to wait instead of degrading.
*What*?! Certainly
to degrade.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it belongs.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
All,
To make this easier for everyone to participate in, I've created a wiki
page:
https://wiki.postgresql.org/wiki/9.4CF4Triage
Please add the patches you know well to the appropriate list, thanks!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers
are reasonable for us to pursue.
What's a bad idea is adding an auto-degrade option without any tools to
manage and monitor it, which is what this patch does by my reading. If
I'm wrong, then someone can point it out to me.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
of
answering questions like is the replica down or just slow?, control
degrade.
Oh, wait! We DO have such a command. It's called ALTER SYSTEM SET!
Recently committed. So this is really a solvable issue if one is
willing to use an external utility.
--
Josh Berkus
PostgreSQL Experts Inc.
http
On 01/10/2014 01:34 PM, David Rowley wrote:
On Sat, Jan 11, 2014 at 8:28 AM, Josh Berkus j...@agliodbs.com wrote:
All,
To make this easier for everyone to participate in, I've created a wiki
page:
https://wiki.postgresql.org/wiki/9.4CF4Triage
Please add the patches you know well
additional monitoring or management infrastructure at all**.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
doesn't support JSONB
for 9.4, we should postpone it to 9.5. We really don't want to get into
a situation where we need an Hstore3 because we accepted an Hstore2
which needs to be rev'd for JSON.
Especially since there's no good reason for the JSON changes not to be
merged already.
--
Josh Berkus
be in a position of archiving two different versions of the same
segment.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
in this order:
1. do immediately
2. do after (1) is complete
3. assign 1 senior hacker reviewer to each patch
4. review as time permits after 1-3
5. review as time permits after 1-3
Let the triage begin!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing
On 01/08/2014 11:07 AM, David Fetter wrote:
On Wed, Jan 08, 2014 at 10:45:37AM -0800, Josh Berkus wrote:
Hackers,
Per the Developer Meeting, we are scheduled to do a final triage of 9.4
patches the week before CF4 starts, which is *now*. The goal of this
triage is to divide patches already
/updated stuff which comes in in the first 48 hours of the
CF. If we wait until the CF begins, we'll spend at least the first week
of the CF triaging.
That's why we set this schedule at the developer meeting.
And besides, we already know what category *your* patch belongs in ...
--
Josh Berkus
useless). However, I seriously
doubt that someone is going to code that up in the next 5 days.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On 01/08/2014 02:04 PM, Peter Eisentraut wrote:
Anyone else?
Or you'll have to deal with me again?
I vote for Peter.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
On 01/08/2014 01:49 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
If we really want auto-degrading sync rep, then we'd (at a minimum) need
a way to determine *from the replica* whether or not it was in degraded
mode when the master died. What good do messages to the master log do
-degrade is coming from users who
don't know what sync rep is for in the first place. The fact that other
vendors are offering auto-degrade as a feature instead of the ginormous
foot-gun it is adds to the confusion, but we can't help that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
the
different sync modes and per-transaction sync). Anything short of that
is just going to muddy the waters further.
Mind you, someone needs to take a machete to the HA section of the docs
anyway.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list
loss as long as
you lose N-1 servers or fewer. And it becomes an even
lower-availability solution if you don't have at least N+1 replicas.
For that reason, I'd like to see some realistic actual user demand
before we take the idea seriously.
--
Josh Berkus
PostgreSQL Experts Inc.
http
of PostgreSQL:
1. Write a few of your own C functions, including trigger functions and
an operator.
2. Write your own foreign data wrapper for something.
3. Write your own Type, including input/output functions, stats
estimation and custom indexing.
--
Josh Berkus
PostgreSQL Experts Inc.
http
make our Python users happy.
And for that matter would get rid of this kind of stupid thing in stored
procedure code:
time_ahead := ( interval '1 minute' * var_skip );
So, +1 for the feature.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list
On 12/20/2013 03:09 PM, Gavin Flower wrote:
What about leap years?
What about them?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On 12/20/2013 04:44 PM, Gavin Flower wrote:
On 21/12/13 13:40, Josh Berkus wrote:
On 12/20/2013 03:09 PM, Gavin Flower wrote:
What about leap years?
What about them?
some years have 365 days others have 366, so how any days in an interval
of 2 years?, 4 years?
Your question isn't relevant
in READ COMMITTED mode, an exception occurs. If it's
set to off, then assertions are disabled, in order to deal with buggy
assertions.
Now, it would be even better if we could prevent users from switching
transaction mode, but that's a MUCH bigger and more complicated patch.
--
Josh Berkus
(or
even a whole-database basis) every time an assertion executed, no?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, most notably Hibernate, check this rows-returned
count, and error if they don't match the rows sent.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
to do just what you propose. Nobody ever worked out
all the practicalities and gotchas to make it really work in production,
though.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Any other votes?
I still support this patch (as I did originally), and don't think that
the overlap with pgFincore is of any consequence. pgFincore does more
than pgrewarm ever will, but it's also platform-specific, so it still
makes sense for both to exist.
--
Josh Berkus
PostgreSQL Experts Inc
.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 12/17/2013 01:42 PM, Kevin Grittner wrote:
Josh Berkus j...@agliodbs.com wrote:
Going back over this patch, I haven't seen any further discussion of the
point Heikki raises above, which seems like a bit of a showstopper.
Heikki, did you have specific ideas on how to solve this? Right now
is completely
something other than what it is. I don't have a better name offhand,
but that's got to change before it becomes a feature.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
On 12/16/2013 10:53 AM, Josh Berkus wrote:
Some PostgreSQL shops with lots of servers have large internal libraries
of functions, views, and similar code that they've written to support
their applications, which don't comprise a complete database. This
feature would allow them to package
Hackers,
I've looked in the archives, but I can't find a reason why INSTEAD OF
triggers were never enabled for tables. I'm interested in them in order
to return a rowcount to JDBC for INSERTs into partitioned tables.
Was there a technical obstacle, or is this just a TUIT issue?
--
Josh Berkus
On 12/16/2013 04:22 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
I've looked in the archives, but I can't find a reason why INSTEAD OF
triggers were never enabled for tables.
What would that mean exactly? And how would you do the actual update
when it came time to?
Well, I'm
(if any), and why Frost doesn't like it. I tried
reading through the thread on -hackers, and came away even more confused.
Is there maybe a wiki page for it?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
is slow?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
frequency of a value
and assumed frequency. However, with highly grouped values, you might
have a 2:1 ratio.
Again, more math (backed by statistical analysis) is needed.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
, really
important ones. Speaking as someone who does trainings for new DBAs,
the part where I do what to look for in the logs requires over an hour
and still doesn't cover everything. And doesn't internationalize. That's
nasty.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent
There is an inherent tuning and troubleshooting challenge in anything
involving a feedback loop.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
in the future.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 12/11/2013 12:40 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
And, for that matter, accepting this patch by no means blocks doing
something more sophisticated in the future.
Yeah. I think the only real argument against it is do we really need
yet another knob?. Since Josh
at a reasonable size, and even then I'll bet we have to offer
a GUC.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Andres, all:
We've just run across a case of this exact issue on 9.2.4. I thought it
was supposed to be 9.3-only?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 12/10/2013 10:39 AM, Andres Freund wrote:
Hi,
On 2013-12-10 10:38:32 -0800, Josh Berkus wrote:
We've just run across a case of this exact issue on 9.2.4. I thought it
was supposed to be 9.3-only?
Could you please describe this exact issue?
Fatal errors due to missing pg_subtrans
...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 12/10/2013 10:48 AM, Andres Freund wrote:
On 2013-12-10 10:44:30 -0800, Josh Berkus wrote:
On 12/10/2013 10:39 AM, Andres Freund wrote:
Hi,
On 2013-12-10 10:38:32 -0800, Josh Berkus wrote:
We've just run across a case of this exact issue on 9.2.4. I thought it
was supposed to be 9.3
.
As discussed, we need math though. Does anyone have an ACM subscription
and time to do a search? Someone must. We can buy one with community
funds, but no reason to do so if we don't have to.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list
of one, offhand. And +1 for NOT adding a new knob.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
sampled are
representative of the population.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
You do seem kind of hostile to the idea of full-page-sampling, going
pretty far beyond the I'd need to see the math. Why?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
. Nobody has done an analysis of whether it's worse, on average, to
estimate low vs. high for ndistinct.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
recoginze common distribution
patterns, then not only could we have better query estimates, those
would require keeping *fewer* stats, since all you need for a normal
distribution are the end points and the variance.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
All,
I tested out Joe's original patch, and it does eliminate the 8%
performance regression.
Will try the new one.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
syntax alternatives we're talking
about here? I've lost track.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
manage that have already said that MMAP is a bad interface for
persistent RAM. They haven't defined a good one, though.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 12/05/2013 05:48 AM, Stephen Frost wrote:
* Peter Geoghegan (p...@heroku.com) wrote:
On Wed, Dec 4, 2013 at 11:07 AM, Josh Berkus j...@agliodbs.com wrote:
But you know what? 2.6, overall, still performs better than any kernel
in the 3.X series, at least for Postgres.
What about the fseek
feature added.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
when PostgreSQL encounters a bug, data
corrpution, or platform error. Right now, I have to suss those out by
regex.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 12/05/2013 12:41 PM, Robert Haas wrote:
On Thu, Dec 5, 2013 at 12:54 PM, Josh Berkus j...@agliodbs.com wrote:
Actually, I've been able to do 35K TPS on commodity hardware on Ubuntu
10.04. I have yet to go about 15K on any Ubuntu running a 3.X Kernel.
The CPU scheduling on 2.6 just seems
801 - 900 of 4746 matches
Mail list logo
