Ideas for improving Concurrency testing
1. Synchronization points in server code - To have better control for
concurrency testing, define synchronization points in server code which can
be used as follows:
On 26.03.2013 02:02, Tom Lane wrote:
Heikki Linnakangashlinnakan...@vmware.com writes:
On 25.03.2013 15:36, Tom Lane wrote:
Heikki Linnakangasheikki.linnakan...@iki.fi writes:
Add PF_PRINTF_ATTRIBUTE to on_exit_msg_fmt.
Per warning from -Wmissing-format-attribute.
Hm, this is exactly
Darren Duncan wrote:
The standard defines UNIQUE on the basis of the UNIQUE predicate:
unique predicate ::= UNIQUE table subquery
and states:
1) Let T be the result of the table subquery.
2) If there are no two rows in T such that the value of each column
in one row is non-null and is not
On 26 March 2013 01:35, Greg Stark st...@mit.edu wrote:
On Tue, Mar 26, 2013 at 12:00 AM, Simon Riggs si...@2ndquadrant.com wrote:
I'll bet you all a beer at PgCon 2014 that this remains unresolved at
that point.
Are you saying you're only interested in working on it now? That after
9.3 is
On 30.12.2012 08:31, Daniel Farina wrote:
A version implementing that is attached, except I generate an
additional 64-bit session not exposed to the client to prevent even
casual de-leaking of the session state. That may seem absurd, until
someone writes a tool that de-xors things and relies on
On Tue, Mar 26, 2013 at 5:27 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 26 March 2013 01:35, Greg Stark st...@mit.edu wrote:
On Tue, Mar 26, 2013 at 12:00 AM, Simon Riggs si...@2ndquadrant.com wrote:
I'll bet you all a beer at PgCon 2014 that this remains unresolved at
that point.
Are
Le lundi 25 mars 2013 19:35:12, Daniel Farina a écrit :
On Mon, Mar 25, 2013 at 11:07 AM, Stefan Kaltenbrunner
ste...@kaltenbrunner.cc wrote:
Back when we used CVS for quite a few years I kept 7 day rolling
snapshots of the CVS repo, against just such a difficulty as this. But
we seem to
On Sun, Mar 24, 2013 at 10:02 PM, Josh Berkus j...@agliodbs.com wrote:
On 03/20/2013 04:45 PM, Brendan Jurd wrote:
Incompatibility:
This patch introduces an incompatible change in the behaviour of the
aforementioned array functions -- instead of returning NULL for empty
arrays they return
2013/3/26 Robert Haas robertmh...@gmail.com:
On Sun, Mar 24, 2013 at 10:02 PM, Josh Berkus j...@agliodbs.com wrote:
On 03/20/2013 04:45 PM, Brendan Jurd wrote:
Incompatibility:
This patch introduces an incompatible change in the behaviour of the
aforementioned array functions -- instead of
On 26 March 2013 11:33, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 26, 2013 at 5:27 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 26 March 2013 01:35, Greg Stark st...@mit.edu wrote:
On Tue, Mar 26, 2013 at 12:00 AM, Simon Riggs si...@2ndquadrant.com wrote:
I'll bet you all a beer
On 26 March 2013 22:57, Robert Haas robertmh...@gmail.com wrote:
They hate it twice as much when the change is essentially cosmetic.
There's no functional problems with arrays as they exist today that
this change would solve.
We can't sensibly test for whether an array is empty. I'd call
On Tue, Mar 26, 2013 at 7:30 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 26 March 2013 11:33, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 26, 2013 at 5:27 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 26 March 2013 01:35, Greg Stark st...@mit.edu wrote:
On Tue, Mar 26, 2013 at
My current master segfaults with pg_dump when dumping a 9.1 or 9.2 database:
$ LC_ALL=en_US.utf8 pg_dump -s -p 5448
pg_dump: column number -1 is out of range 0..22
zsh: segmentation fault LC_ALL=en_US.utf8 pg_dump -s -p 5448
The reason seems to be that getTables() in pg_dump.c forget to select
On 26.03.2013 15:31, Bernd Helmle wrote:
My current master segfaults with pg_dump when dumping a 9.1 or 9.2
database:
$ LC_ALL=en_US.utf8 pg_dump -s -p 5448
pg_dump: column number -1 is out of range 0..22
zsh: segmentation fault LC_ALL=en_US.utf8 pg_dump -s -p 5448
The reason seems to be that
Simon Riggs si...@2ndquadrant.com writes:
So please, lets go with a simple solution now that allows users to say
what they want.
Simon, this is just empty posturing, as your arguments have nothing
whatsoever to do with whether the above description applies to your
patch.
More generally, the
The core team has received word of a seriously nasty security problem
in recent releases of Postgres. We will be wrapping update releases
to fix this next week, following the new usual schedule of tarball
wrap Monday afternoon EDT, public announcement Thursday (4/4).
Committers are reminded that
On 26 March 2013 14:44, Tom Lane t...@sss.pgh.pa.us wrote:
Simon Riggs si...@2ndquadrant.com writes:
So please, lets go with a simple solution now that allows users to say
what they want.
Simon, this is just empty posturing, as your arguments have nothing
whatsoever to do with whether the
Fujii Masao masao.fu...@gmail.com wrote:
Ping? ISTM this problem has not been fixed in HEAD yet.
It's next on my list. The other reports seemed more serious and
more likely to be contentious in terms of the best fix.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
On Tue, Mar 26, 2013 at 7:31 AM, Amit Kapila amit.kap...@huawei.com wrote:
Above ideas could be useful to improve concurrency testing and can also be
helpful to generate test cases for some of the complicated bugs for which
there is no direct test.
I wonder how much explicit sync points would
On Fri, Mar 22, 2013 at 06:06:18PM +, Greg Stark wrote:
On Fri, Mar 22, 2013 at 2:02 PM, Tom Lane t...@sss.pgh.pa.us wrote:
And we definitely looked at ARC
We didn't just look at it. At least one release used it. Then patent
issues were raised (and I think the implementation had some
On Fri, Mar 22, 2013 at 04:16:18PM -0400, Tom Lane wrote:
Merlin Moncure mmonc...@gmail.com writes:
I think there is some very low hanging optimization fruit in the clock
sweep loop. first and foremost, I see no good reason why when
scanning pages we have to spin and wait on a buffer in
On Tue, Mar 26, 2013 at 11:40 AM, Bruce Momjian br...@momjian.us wrote:
On Fri, Mar 22, 2013 at 04:16:18PM -0400, Tom Lane wrote:
Merlin Moncure mmonc...@gmail.com writes:
I think there is some very low hanging optimization fruit in the clock
sweep loop. first and foremost, I see no good
On Tue, Mar 26, 2013 at 03:06:30PM +, Simon Riggs wrote:
More generally, the fact that a patch has some user-frobbable knob
does not mean that it's actually a good or even usable solution. As
everybody keeps saying, testing on a wide range of use-cases would be
needed to prove that,
On 2013.03.26 1:40 AM, Albe Laurenz wrote:
Darren Duncan wrote:
So, determining if 2 rows are the same involves an iteration of dyadic logical
AND over the predicates for each column comparison. Now logical AND has an
identity value, which is TRUE, because TRUE AND p (and p AND TRUE) results
On 26.03.2013 09:51, Heikki Linnakangas wrote:
On 26.03.2013 02:02, Tom Lane wrote:
Heikki Linnakangashlinnakan...@vmware.com writes:
On 25.03.2013 15:36, Tom Lane wrote:
Heikki Linnakangasheikki.linnakan...@iki.fi writes:
Add PF_PRINTF_ATTRIBUTE to on_exit_msg_fmt.
Per warning from
On Tue, Mar 19, 2013 at 9:19 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
If failures happen with CREATE INDEX CONCURRENTLY, the system will be let
with invalid indexes. I don't think that the user would like to see invalid
indexes of
an existing system being recreated as valid after a
Merlin Moncure mmonc...@gmail.com wrote:
*) For off-cycle release work that would help enable patches with
complex performance trade-offs (I'm working up another patch that has
even more compelling benefits and risks in the buffer allocator), We
desperately need a standard battery of
Heikki Linnakangas wrote:
This is what I came up with. I created a new file, misc.c (for lack
of a better name), for things that are shared by pg_dump and
pg_restore, but not pg_dumpall or other programs. I moved all the
parallel stuff from dumputils.c to parallel.c, and everything else
On Sun, Mar 24, 2013 at 12:37 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Sat, Mar 23, 2013 at 10:20 PM, Andres Freund and...@2ndquadrant.com
wrote:
On 2013-03-22 07:38:36 +0900, Michael Paquier wrote:
Is someone planning to provide additional feedback about this patch at
On 27/03/13 06:14, Darren Duncan wrote:
On 2013.03.26 1:40 AM, Albe Laurenz wrote:
Darren Duncan wrote:
So, determining if 2 rows are the same involves an iteration of
dyadic logical
AND over the predicates for each column comparison. Now logical AND
has an
identity value, which is TRUE,
Hi all!
I finally started to investigate why spoonbill stopped reporting to the
buildfarm feedback about 2 months ago.
It seems that the foreign-keys locking patch (or something commity very
close to January 23th) broke it in a fairly annoying way - running the
buildfarm script seems to
Robert Haas escribió:
On Wed, Mar 20, 2013 at 5:42 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Here's a new version of this patch, rebased on top of the new
pg_identify_object() stuff. Note that the regression test doesn't work
yet, because I didn't adjust to the new identity
Alvaro Herrera alvhe...@2ndquadrant.com writes:
Now there *is* one rather big performance problem in this patch, which
is that it turns on collection of object dropped data regardless of
there being event triggers that use the info at all. That's a serious
drawback and we're going to get
I expect to lose this argument, but I think this is a terrible idea.
Users really hate it when they try to upgrade and find that they, uh,
can't, because of some application-level incompatibility like this.
They hate it twice as much when the change is essentially cosmetic.
There's no
Hello all
2013/3/26 Tom Lane t...@sss.pgh.pa.us:
Josh Berkus j...@agliodbs.com writes:
Where are we with this patch? I'm a bit unclear from the discussion on
whether it passes muster or not. Things seem to have petered out.
I took another look at this patch tonight. I think the thing that
Tom Lane escribió:
Alvaro Herrera alvhe...@2ndquadrant.com writes:
Now there *is* one rather big performance problem in this patch, which
is that it turns on collection of object dropped data regardless of
there being event triggers that use the info at all. That's a serious
drawback and
On Tue, Mar 26, 2013 at 3:02 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I tried this and it doesn't work. The error pathways you speak about
would be the xact.c entry points to commit and abort transactions;
however, there's a problem with that because some of the commands that
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
I finally started to investigate why spoonbill stopped reporting to the
buildfarm feedback about 2 months ago.
It seems that the foreign-keys locking patch (or something commity very
close to January 23th) broke it in a fairly annoying way -
On Tue, Mar 26, 2013 at 9:02 AM, Brendan Jurd dire...@gmail.com wrote:
On 26 March 2013 22:57, Robert Haas robertmh...@gmail.com wrote:
They hate it twice as much when the change is essentially cosmetic.
There's no functional problems with arrays as they exist today that
this change would
Hello!
I'm an IT student, and I would like to apply for the 2013 GSoC.
I've been looking at this mailing list for a while now, and I saw a
suggestion for GSoC that particularly interested me: implementing the
K-medoids clustering in Madlib, as it is supposed to be more efficient than
the K-means
Robert Haas escribió:
On Tue, Mar 26, 2013 at 3:02 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Now there *is* one rather big performance problem in this patch, which
is that it turns on collection of object dropped data regardless of
there being event triggers that use the info at
On 03/26/2013 08:45 PM, Tom Lane wrote:
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
I finally started to investigate why spoonbill stopped reporting to the
buildfarm feedback about 2 months ago.
It seems that the foreign-keys locking patch (or something commity very
close to January
Alvaro Herrera alvhe...@2ndquadrant.com wrote:
Not happy with misc.c as a filename.
We already have two misc.c files:
src/backend/utils/adt/misc.c
src/interfaces/ecpg/ecpglib/misc.c
I much prefer not to repeat the same filename in different
directories if we can avoid it.
How about
On 2013-03-26 13:14:53 -0700, Kevin Grittner wrote:
Alvaro Herrera alvhe...@2ndquadrant.com wrote:
Not happy with misc.c as a filename.
We already have two misc.c files:
src/backend/utils/adt/misc.c
src/interfaces/ecpg/ecpglib/misc.c
I much prefer not to repeat the same filename in
Using HEAD's pg_dump, I see pg_dump -s regression taking 5 seconds.
On the other hand, running the same executable against the regression
database on a 9.2 postmaster takes 1.2 seconds. Looks to me like we
broke something performance-wise.
A quick check with oprofile says it's all
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
On 03/26/2013 08:45 PM, Tom Lane wrote:
It looks from here like the isolationtester client is what's dropping
the ball --- the backend states are unsurprising, and two of them are
waiting for a new client command. Can you get a stack trace
On 27 March 2013 06:47, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 26, 2013 at 9:02 AM, Brendan Jurd dire...@gmail.com wrote:
We can't sensibly test for whether an array is empty. I'd call that a
functional problem.
Sure you can. Equality comparisons work just fine.
rhaas=#
Robert Haas robertmh...@gmail.com writes:
Well, you could easily change array_ndims() to error out if ARR_NDIM()
is negative or more than MAXDIM and return NULL only if it's exactly
0. That wouldn't break backward compatibility because it would throw
an error only if fed a value that
On 03/26/2013 02:50 PM, Stefan Kaltenbrunner wrote:
Hi all!
I finally started to investigate why spoonbill stopped reporting to the
buildfarm feedback about 2 months ago.
It seems that the foreign-keys locking patch (or something commity very
close to January 23th) broke it in a fairly
On 3/24/13 3:10 PM, Tom Lane wrote:
I also concur with the complaint here
http://www.postgresql.org/message-id/caazkufzxyj-rt1aec6s0g7zm68tdlfbbm1r6hgrbbxnz80k...@mail.gmail.com
that allowing a minimum sleep of 0 is rather dangerous
The original watch command apparently silently corrects a
Andrew Dunstan and...@dunslane.net writes:
There is some timeout code already in the buildfarm client. It was
originally put there to help us when we got CVS hangs, a not infrequent
occurrence in the early days, so it's currently only used if configured
for the checkout phase, but it could
Tom Lane t...@sss.pgh.pa.us wrote:
Using HEAD's pg_dump, I see pg_dump -s regression taking 5
seconds.
On the other hand, running the same executable against the regression
database on a 9.2 postmaster takes 1.2 seconds. Looks to me like we
broke something performance-wise.
A quick check
Michael Paquier michael.paqu...@gmail.com writes:
On top of checking indisvalid, I think that some additional checks on
indislive and indisready are also necessary.
Those are not necessary, as an index that is marked indisvalid should
certainly also have those flags set. If it didn't require
On 03/26/2013 09:33 PM, Tom Lane wrote:
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
On 03/26/2013 08:45 PM, Tom Lane wrote:
It looks from here like the isolationtester client is what's dropping
the ball --- the backend states are unsurprising, and two of them are
waiting for a new
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
hmm - will look into that in a bit - but I also just noticed that on the
same day spoonbill broke there was also a commit to that file
immediately before that code adding the fflush() calls.
It's hard to see how those would be related to
On Wed, Mar 27, 2013 at 6:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Michael Paquier michael.paqu...@gmail.com writes:
On top of checking indisvalid, I think that some additional checks on
indislive and indisready are also necessary.
Those are not necessary, as an index that is marked
On Tue, 2013-03-26 at 02:50 +0900, Fujii Masao wrote:
Hi,
I found that the regression test failed when I created the database
cluster with the checksum and set wal_level to archive. I think that
there are some bugs around checksum feature. Attached is the regression.diff.
Thank you for the
On 25 March 2013 17:50, Fujii Masao masao.fu...@gmail.com wrote:
I found that the regression test failed when I created the database
cluster with the checksum and set wal_level to archive. I think that
there are some bugs around checksum feature. Attached is the regression.diff.
Apologies for
On 26 March 2013 23:23, Jeff Davis pg...@j-davis.com wrote:
Patch attached. Only brief testing done, so I might have missed
something. I will look more closely later.
Thanks, I'll look at that tomorrow.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development,
On 25 March 2013 19:14, Heikki Linnakangas hlinnakan...@vmware.com wrote:
Simon, can you comment on this?
Yes, will do.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training Services
--
Sent via pgsql-hackers mailing list
I suggested a couple of algorithms to be implemented in MADLib(apart
from K Medoids). You could pick some(or all) of them, which would
require 3 months to be completed.
As for more information on index, you can refer
http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.1
along with the
Atri Sharma atri.j...@gmail.com writes:
I suggested a couple of algorithms to be implemented in MADLib(apart
from K Medoids). You could pick some(or all) of them, which would
require 3 months to be completed.
As for more information on index, you can refer
On Tue, Mar 26, 2013 at 10:27 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Atri Sharma atri.j...@gmail.com writes:
I suggested a couple of algorithms to be implemented in MADLib(apart
from K Medoids). You could pick some(or all) of them, which would
require 3 months to be completed.
As for more
63 matches
Mail list logo
