the original problem.
Has this patch had performance testing? Because of the list crossover I
don't have any information on that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
.
Searching email for patches is, at best, inexact.
--
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
just because I didn't see his patch.
--
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
a bajillion hidden
columns, and for a bonus we'd save substantially on catalog bloat.
Where are we on this patch? Should I mark it Returned and you'll work
on it for September?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
columns, where column #390 was
null and gets updated to a not null value
I don't *think* that Jamie's performance tests have really addressed the
above cases. However, do people agree that if performance on the patch
passes for all of A, B and C, then it's OK to apply?
--
Josh Berkus
PostgreSQL
actually preallocate fewer segments than the old formula.
Since I haven't seen a reply to Peter's comments from Heikki, I'm
marking this patch returned with feedback. I know, it's a very busy
CF, and I'm sure that you just couldn't get back to this one. We'll
address it in September?
--
Josh
these things in the next couple days?
Otherwise, I would like to mark this returned with feedback, and you can
submit an updated patch to the next CommitFest.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
an update on this in 10 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/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
presented a nice spec
some time ago (Robert and I liked it) which would break backward
compatibility but allow to begin with a fresh infrastructure.
As folks know, I favor Smith's approach. However, as far as I can find,
GSmith never posted a patch for his version.
--
Josh Berkus
PostgreSQL
features nor spec compliance.
Where are we with this patch? Fabien, are you going to submit an
updated version which addresses the objections, or should I mark it
Returned With Feedback?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql
be different form
deciding to separate this estimation function from that for
analyze.
Kyotaro, do you think you'll be revising this patch in the next 2 days,
or should I bounce it, and you can resubmit it for the next commitfest?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
of 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/pgsql-hackers
days, or does it bounce?
--
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
documentation for the GUC variable
'wal_update_compression_ratio'?
Yes.
--
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 start reviewing!
Since these are cloud servers, they won't work well for performance
testing. However, they will be excellent for testing replication.
If you need one of these, please contact me to allocate a VM for you.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent
(idea is
workable, but the given implementation is not).
Exactly.
--
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
/4ee91248.8010...@2ndquadrant.com
So, this seems to still be stalled. Is there a way forward on this
which won't cause us to wait *another* version before we have working
replication GUCs?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On 07/05/2013 09:08 AM, Peter Eisentraut wrote:
On 7/3/13 7:15 PM, Josh Berkus wrote:
I'm not comfortable with having all of the transform mappings in the
main contrib/ directory though. Can we add a subdirectory called
transforms containing all of these?
I don't see any value
instructions.
--
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
instead of connecting directly to Postgres.
--
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 the
future tie in to being able to dispatch asyncronous queries from psql.
If we have a query result cache, it's one short step to allowing that
result cache to be populated asyncrhonously.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql
On 07/03/2013 07:43 AM, Robert Haas wrote:
Let's have a new schedule called minute-check with the objective to run the
common tests in 60 secs.
Note that we're below 60s even with assert and CLOBBER_CACHE_ALWAYS, at
least on my laptop.
--
Josh Berkus
PostgreSQL Experts Inc.
http
the CF started and I found myself doing the patch
sweep the day before the CF, which didn't leave time for an email response.
This is one of those areas where better tooling could help a lot.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list
so that they can tell their bosses that
they *have* to spend time on patch review. Otherwise, the review
doesn't happen.
--
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
ever end up
doing a list again.
--
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
Hackers,
Please, oh please, won't someone review this? This patch has been 3
years in the making, so I suspect that it will NOT be a fast review.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
. Can someone with more knowledge of the
extension facility comment on that?
I believe that's correct.
--
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
Peter, Cedric, etc.:
Where are we on this patch? Seems like discussion died out. Should it
be bounced?
--
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
time.
That's a good point. I hadn't considered (or realized the extent of)
the occasional and specific nature of Michael's involvement with the
project these days. My apologies, then, Michael.
Is there anyone else on the committer list with similar circumstances?
--
Josh Berkus
PostgreSQL
Liming,
Given that this patch will not be ready for commit this week, but has
gotten a review, I am marking it as Returned with Feedback. Please
keep working on it, and as soon as you have a new version of the patch,
add it to the September commitfest. Thanks!
--
Josh Berkus
PostgreSQL
containing all of these?
--
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 07/03/2013 04:05 PM, Alvaro Herrera wrote:
Josh Berkus escribió:
Liming,
Given that this patch will not be ready for commit this week, but has
gotten a review, I am marking it as Returned with Feedback. Please
keep working on it, and as soon as you have a new version of the patch,
add
into a rut of letting a handful of people do 90% of the
reviewing, resulting in CFs which last forever and some very frustrated
major contributors. That part shouldn't be necessary again for some
time, hopefully.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
On 07/01/2013 12:05 AM, ian link wrote:
Definitely not this week. Hopefully for next commit fest.
OK, marked Returned with Feedback. It'll be up to you to add it to
the next commitfest if you think it's ready by then.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent
tests for the next 3 months, and so that Andrew can
work on the buildfarm additions.
--
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
I thought that Jeff withdrew this patch.
He did, but nobody removed it from the commitfest --- partly because of
a change of subject line breaking the thread.
Bounced to returned with feedback now.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers
. I think I will address those
after the opclass stuff is done.
Are these things you plan to get done this week, or for next CommitFest?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
else, then go for 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
then that path is used instead of a
path inferred from the name of the Makefile.
SO is this patch returned with feedback?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
is abysmal, and I think I'm starting to see 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:
http://www.postgresql.org/mailpref/pgsql-hackers
we want to include the core tests in those?
--
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 pervasive use case. If Alvaro gets to it, I think the updating the
range, rescan at VACUUM time approach isn't much more complex, but if
he doesn't I'd still vote to accept the feature.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
!
Thank you.
Greg, are you still working on those tests?
Since Greg seems to be busy, what needs to be done to test this?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
are qualified to review any of the above, please get started
*now*, and leave the non-performance patches for later;
(2) ideas on how we can speed up/parallelize performance testing efforts
are extremely welcome.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
that creates a view
test: rules
--
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 06/28/2013 12:42 PM, Josh Berkus wrote:
On 05/13/2013 05:37 PM, Robins Tharakan wrote:
Hi,
Patch to add more regression tests to ASYNC (/src/backend/commands/async).
Take code-coverage from 39% to 75%.
This isn't applying for me anymore due to changes in the
parallel_schedule file
... FAILED
Thoughts?
--
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
seconds per run
on my laptop), in order to greatly improve regression test coverage.
I'd say that splitting the tests is not warranted, and that we should go
ahead with these tests on their testing merits, not based on any extra
check time they might add.
--
Josh Berkus
PostgreSQL Experts Inc.
http
checkout the latest revision and submit this patch again.
I was only checking test timing, per my earlier email. I haven't looked
at the tests themselves at all.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
checkout the latest revision and submit this patch again.
I was only checking test timing, per my earlier email. I haven't looked
at the tests themselves at all.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
, it would require 15
more patch sets the size of Robins' to get there, so I don't see that
it's worth the trouble any time soon.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
reviewers to do more reviews.
But that would only work if we're also giving reviewers credit; as
several people have said, they care more about credit than they do about
prizes.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
All,
So, is this patch currently depending on performance testing, or not?
Like I said, it'll be a chunk of time to set up what I beleive is a
realistic performance test, so I don't want to do it if the patch is
likely to be bounced for other reasons.
--
Josh Berkus
PostgreSQL Experts Inc.
http
If we're going to try harder to ensure that reviewers are credited,
it'd probably be better to take both the commit log and the release
notes out of that loop.
I'd pull the reviewers out of the CF app. Even in its current
implementation, that's the easiest route.
--
Josh Berkus
PostgreSQL
permissions on LISTEN/NOTIFY period. However, I'd like to see
separate permissions on LISTEN and NOTIFY; I can easily imagine wanting
to grant a user one without the other.
Also, someone would need to do performance tests to see how much the
permissions check affects performance.
--
Josh Berkus
of
100 random column positions = some value
4) time required to insert 1000 rows
5) time required to update 1000 rows
Geez, I feel tired just thinking about it. Jamie, can your team do any
of this?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing
doesn't have a
full report from you.
Thanks!
--
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 tests pass,
the test coverage increses as provided.? Or do you expect some more info?
Yes, mainly:
a) does it test what it purports to test?
b) do the tests pass on your machine?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql
patch, get listed after the original patch author with the
patch, and reviewers do more lightweight reviews get listed at the
bottom of the release notes? Seems fair to me.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
systematically, and I feel that it
would be sad if they were lost.
My thinking was that someone should add all of his new tests at once,
and then see how much of a time difference they make. If it's 7
seconds, who cares?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via
discussion which blocks commit are waiting on author
rather than some other status. It was not clear to me (or to Mike) that
the dicussion on this patch was concluded favorably. Is it?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql
working again.
--
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
, as a
promotion to increase the number of non-submitter reviewers?
a) yes
b) no
c) yes, but submitters and committers should get it too
Thanks for your feedback!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
and without the horrible logistics issues of mailing
tshirts to 15 countries.
--
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
NOT have a shortage of patch submitters. Seems
like we should apply incentives where we need help, no?
Mind you, my votes are (B), (A), and (A).
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
...
We have access to attorneys, both in the US and Canada. I will proceed
to ask for real legal advice.
However, can you tell me what exactly you are concerned about? lz4 is
under the BSD license, and released by Google. Why are we worried, exactly?
--
Josh Berkus
PostgreSQL Experts Inc.
http
On 06/25/2013 12:23 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
However, can you tell me what exactly you are concerned about? lz4 is
under the BSD license, and released by Google. Why are we worried, exactly?
Patents. The license on the code doesn't matter --- worst case
. Please plow ahead.
--
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
this feature? Will being non-spec
introduce migration pain?
--
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
, this isn't stopping the patch; I just want a TODO for implement
WITH ORDINALITY in the target list for SRFs.
--
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
emails yesterday, I am trying to make sure that this CF
finishes on time. Following the rules passed at the developer meetings
for how CFs are to be run, I am doing so. If the result is
unsatisfactory, I can always resign as CFM.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent
On 06/24/2013 10:02 AM, Dimitri Fontaine wrote:
Josh Berkus j...@agliodbs.com writes:
patch. The vast majority chose not to respond to my email to them at
all. When private email fails, the next step is public email.
The only problem I have here is that I don't remember about deciding
from abroad.
I have previously proposed that all of the reviewers of a given
PostgreSQL release be honored in the release notes as a positive
incentive, and was denied on this from doing so. Not coincidentally, we
don't seem to have any reviewers-at-large anymore.
--
Josh Berkus
PostgreSQL
with one
hand tied behind my back. That's what I'm saying.
--
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
transparently clear to those folks' bosses that they have to give their
staff time for patch review if they expect to get the features *they*
want into PostgreSQL.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
review it within 5 days or else policy combined with a ton of
my own work has kept me back so far.
Thanks! Your help is much appreciated, on whatever schedule you can do it!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
money, you know.
--
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
a compiled list of reviewers at the end of the
release notes, in the form of:
Reviewers and Testers for #.# Included: name, name, name, name
That way we can pick up the trivial reviewers as well, and even testers
who are not otherwise contributors.
--
Josh Berkus
PostgreSQL Experts Inc.
http
be committing simple patches,
as they won't be able to review others.
Commit a simple patch, review a simple patch. If we have 20 submitters
of simple patches, then we have 20 simple patches to review, no?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers
|
plpython2u | f | f | plpython2_call_handler |
plpython2_inline_handler | plpython2_validator | $libdir/plpython2 |
plpython3u | f | f | plpython3_call_handler |
plpython3_inline_handler | plpython3_validator | $libdir/plpython3 |
(8 rows)
--
Josh
PLs, and for that you don't need a pltemplate entry. It's
likely that pg_pltemplate will disappear entirely before long.
Ah, ok. Thanks!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
was comprehensive; I was planning to develop one myself this week.
--
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
, there are multiple issues with having hundreds of columns, of
which storage optimization is only one ... and probably the smallest one
at that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
.
Anyway, let's decide if acceptance of this patch hinges on performance
or not. I'll take me a whole evening to set up a good performance test,
so I don't want to do it if it's going to be a moot point.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing
that look like, syntactically?
--
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
, XLogInsert scaling, preserving
forensic information when we freeze, remove PD_ALL_VISIBLE. These shoud
be addressed early so that we can work out the conflicts between them.
So, some progress, but more is needed.
--Josh Berkus
CommitFest Manager
--
Josh Berkus
PostgreSQL Experts Inc.
http
, so these folks are not necessarily slackers
(although with Bruce, we know for sure):
Bruce Momjian (momjian)
Michael Meskes (meskes)
Teodor Sigaev (teodor)
Andrew Dunstan (adunstan)
Magnus Hagander (mha)
Itagaki Takahiro (itagaki)
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
FOLLOWING) from foo;
What do you expect SELECT first(val order by ts desc) to output ?
Ah, right, I see what you mean. Yeah, I was doing queries without peer
rows, so it looked the same to me, and it uses some of the same
machinery. But of course it's not completely the same.
--
Josh Berkus
might possibly be SSD).
I'm sure we could use these for the performance test farm. If we need
to replace some of the drives, the community has money for that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
Who can be point of contact from the community to arrange shipping, etc?
I can be.
And I'll handle the tax credit once the servers are received.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On 06/21/2013 02:33 PM, desmodemone wrote:
Hi all,
I see a strange behavior ( for me ) on 9.2 (but seems the same on
9.1 and 9.3) of the optimizer on query like that :
Matteo, I just posted this on -performance. See Tom's answer.
--
Josh Berkus
PostgreSQL Experts Inc.
http
a choice about creating new
function names and then waiting three years to deprecate the old ones.
We really can't afford to put obstacles in the way of people upgrading,
especially over an issue as minor as this one.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql
operation.
--
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
I'd imagine having a CF entry per release, so after a set of minor
releases, the CF is closed.
How would we name these?
Also, what about patches for beta? Should we have a beta CF?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql
On 06/19/2013 10:48 AM, Peter Eisentraut wrote:
On 6/13/13 5:47 PM, Josh Berkus wrote:
2. File name to store settings set by ALTER SYSTEM command is still
persistent.auto.conf
Why? Shouldn't it just be auto.conf? Or system.auto.conf?
I prefer auto.conf, personally.
Well, not much about
ON ALL TO admin;
I can certainly see wanting this, but it'd be a great deal more
sophisticated than what Chris has proposed.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
.
Well, I think that someone needs to actually test doing a sort with,
say, 100GB of RAM and make sure it doesn't crash. Anyone have a machine
they can try that on?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
:
1) short
2) significantly different from postgresql.conf
3) near the beginning of the alphabet, so it should sort near the top if
there are other files in conf/ directory
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On 06/18/2013 10:59 AM, Simon Riggs wrote:
Thanks. Please delete the patch marked Batch API for After Triggers.
All others are submissions by me.
The CF app doesn't permit deletion of patches, so I marked it returned
with feedback.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
1201 - 1300 of 4746 matches
Mail list logo