Hello,
Is the point of this discussion that the patch may leave out some
glich about timing of timeline-related changing and Heikki saw an
egress of that?
AFAIU, the committed patch has some gap in overall scenario which is
the
fast promotion issue.
Right, the fast
Attached herewith is a patch based on description in my previous mail.
This patch would need revision since the error situation in case of
authentication timeout on the server needs to be handled; probably in
simple_prompt()?
--
Amit Langote
--
Sent via pgsql-hackers mailing list
On 16 May 2013 07:02, Kyotaro HORIGUCHI horiguchi.kyot...@lab.ntt.co.jp wrote:
fast promotion issue.
Excuse me for not joining the thread earlier. I'm not available today,
but will join in later in my evening.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL
On Thu, May 16, 2013 at 3:53 PM, Amit Langote amitlangot...@gmail.com wrote:
Attached herewith is a patch based on description in my previous mail.
This patch would need revision since the error situation in case of
authentication timeout on the server needs to be handled; probably in
On Thursday, May 16, 2013 11:33 AM Kyotaro HORIGUCHI wrote:
Hello,
Is the point of this discussion that the patch may leave out
some
glich about timing of timeline-related changing and Heikki saw
an
egress of that?
AFAIU, the committed patch has some gap in overall
Andrew Dunstan and...@dunslane.net writes:
DATA_built = sql/$(EXTENSION)--$(EXTVERSION).sql
DATA = $(filter-out sql/$(EXTENSION)--$(EXTVERSION).sql, $(wildcard
sql/*--*.sql))
Is that right?
I think that's still breaking VPATH builds because the widlcard call
happens in the current tree, not
Hello
I proposed a some months log plans of cancelled queries
http://www.postgresql.org/message-id/cafj8pra-duzkmdtu52ciugb0p7tvri_b8ltjmjfwcnr1lpt...@mail.gmail.com
. After discussion the proposal was changed to get plan of any running
query.
I have a proof concept patch now and I am thinking
On 16 May 2013 11:09, Pavel Stehule pavel.steh...@gmail.com wrote:
Hello
I proposed a some months log plans of cancelled queries
http://www.postgresql.org/message-id/cafj8pra-duzkmdtu52ciugb0p7tvri_b8ltjmjfwcnr1lpt...@mail.gmail.com
. After discussion the proposal was changed to get plan of
2013/5/16 Thom Brown t...@linux.com:
On 16 May 2013 11:09, Pavel Stehule pavel.steh...@gmail.com wrote:
Hello
I proposed a some months log plans of cancelled queries
http://www.postgresql.org/message-id/cafj8pra-duzkmdtu52ciugb0p7tvri_b8ltjmjfwcnr1lpt...@mail.gmail.com
. After discussion the
On 2013-05-16 17:35:10 +0900, Amit Langote wrote:
On Thu, May 16, 2013 at 3:53 PM, Amit Langote amitlangot...@gmail.com wrote:
Attached herewith is a patch based on description in my previous mail.
This patch would need revision since the error situation in case of
authentication timeout on
On 05/16/2013 05:41 AM, Dimitri Fontaine wrote:
Andrew Dunstan and...@dunslane.net writes:
DATA_built = sql/$(EXTENSION)--$(EXTVERSION).sql
DATA = $(filter-out sql/$(EXTENSION)--$(EXTVERSION).sql, $(wildcard
sql/*--*.sql))
Is that right?
I think that's still breaking VPATH builds because the
On Thu, May 16, 2013 at 8:01 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2013-05-16 17:35:10 +0900, Amit Langote wrote:
On Thu, May 16, 2013 at 3:53 PM, Amit Langote amitlangot...@gmail.com
wrote:
Attached herewith is a patch based on description in my previous mail.
This patch
* Heikki Linnakangas (hlinnakan...@vmware.com) wrote:
My theory is that after that point all the cores are busy,
and processes start to be sometimes context switched while holding
the spinlock, which kills performance. Has anyone else seen that
pattern?
Isn't this the same issue which has
* Christoph Berg (c...@df7cb.de) wrote:
That was because the plain ./configure version (for a minimal way to
reproduce) didn't built with debug symbols. The original gcc line from the
Debian build log is:
It did, but Debian (and Ubuntu and friends) pull the debugging symbols
out of the
Re: Stephen Frost 2013-05-16 20130516123344.gt4...@tamriel.snowman.net
* Christoph Berg (c...@df7cb.de) wrote:
That was because the plain ./configure version (for a minimal way to
reproduce) didn't built with debug symbols. The original gcc line from the
Debian build log is:
It did, but
On Wed, May 15, 2013 at 10:36 PM, Jon Nelson jnelson+pg...@jamponi.net wrote:
On Wed, May 15, 2013 at 10:17 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Jon Nelson escribió:
On Wed, May 15, 2013 at 4:46 PM, Jon Nelson jnelson+pg...@jamponi.net
wrote:
That's true. I originally wrote
Josh Berkus j...@agliodbs.com wrote:
It's fairly common for matviews to be constructed such that
updates to them are strictly appends. For example, a matview
which has a daily summary would just get appended to each day,
and existing rows would not change barring a major historical
database
On Wed, May 15, 2013 at 08:49:00PM +0200, Andres Freund wrote:
On 2013-05-13 10:28:59 -0400, Noah Misch wrote:
Each worker needs to make SnapshotNow visibility decisions coherent with the
master. For sorting, this allows us to look up comparison functions, even
when the current transaction
On Tue, May 7, 2013 at 10:23:48AM +0530, Amit Kapila wrote:
2. I am not able to figure out which item of release notes cover the
below
feature commit
Avoid inserting Result nodes that only compute identity projections.
http://www.postgresql.org/message-id/E1UGCBh-0006P3-
Andrew Dunstan and...@dunslane.net writes:
On 05/16/2013 05:41 AM, Dimitri Fontaine wrote:
And VPATH building of extension is crucially important for me, as the
easiest way I've found to build and package a given extension against
all currently supported version of PostgreSQL.
Is there
* Christoph Berg (c...@df7cb.de) wrote:
This wasn't the Debian build, but just plain ./configure --with-perl
without any other arguments. As said in the previous mail, both this
and the Debian build segfault here. (Which means there is no -dbg
package because the build fails.)
Oh, I see what
Maciej Gajewski maciej.gajews...@gmail.com writes:
I find this feature quite useful, but I understand that my use case
may be quite unique.
Just to say that I too find what you've done quite useful. Please add
your patch to the next commit fest for consideration in 9.4!
Regards,
--
Dimitri
Le jeudi 16 mai 2013 15:51:48, Tom Lane a écrit :
Andrew Dunstan and...@dunslane.net writes:
On 05/16/2013 05:41 AM, Dimitri Fontaine wrote:
And VPATH building of extension is crucially important for me, as the
easiest way I've found to build and package a given extension against
all
On Thursday, May 16, 2013 7:17 PM Bruce Momjian wrote:
On Tue, May 7, 2013 at 10:23:48AM +0530, Amit Kapila wrote:
2. I am not able to figure out which item of release notes cover
the
below
feature commit
Avoid inserting Result nodes that only compute identity
projections.
On 05/16/2013 10:39 AM, Cédric Villemain wrote:
Le jeudi 16 mai 2013 15:51:48, Tom Lane a écrit :
Andrew Dunstan and...@dunslane.net writes:
On 05/16/2013 05:41 AM, Dimitri Fontaine wrote:
And VPATH building of extension is crucially important for me, as the
easiest way I've found to build
nel...@monkey.org writes:
RhodiumToad asked me to report pg in PathNameOpenFile / mdopen is
assuming that errno is preserved over calls to free() which is not
required by the spec
Good catch! The proximate problem appears to be this bit in
PathNameOpenFile:
vfdP-fd =
Amit Langote amitlangot...@gmail.com writes:
On Thu, May 16, 2013 at 8:01 PM, Andres Freund and...@2ndquadrant.com wrote:
I unfortunately have to say I don't really see the point of this. The
cost of the additional connection attempt is rather low and we have to
deal with the superflous
Stephen Frost sfr...@snowman.net writes:
Isn't this the same issue which has prompted multiple people to propose
(sometimes with code, as I recall) to rip out our internal spinlock
system and replace it with kernel-backed calls which do it better,
specifically by dealing with issues like the
I wrote:
Let's say there is a table and matview like this:
create table foo (fooid int primary key, val int not null);
create materialized view bar as select distinct val from foo;
Some of the subsequent text doesn't make sense unless that
materialized view has an index, like this:
create
On Fri, May 17, 2013 at 1:05 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Langote amitlangot...@gmail.com writes:
On Thu, May 16, 2013 at 8:01 PM, Andres Freund and...@2ndquadrant.com
wrote:
I unfortunately have to say I don't really see the point of this. The
cost of the additional
On 2013-05-17 01:29:25 +0900, Amit Langote wrote:
On Fri, May 17, 2013 at 1:05 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Langote amitlangot...@gmail.com writes:
On Thu, May 16, 2013 at 8:01 PM, Andres Freund and...@2ndquadrant.com
wrote:
I unfortunately have to say I don't really see
Andres Freund and...@2ndquadrant.com writes:
On 2013-05-17 01:29:25 +0900, Amit Langote wrote:
Can this stay in the future releases for new users of libpq to
consider using it (saving them a reconnection, however small a benefit
that is) or at least psql which is being changed to use it
Andrew Dunstan wrote:
On 05/16/2013 10:39 AM, Cédric Villemain wrote:
Le jeudi 16 mai 2013 15:51:48, Tom Lane a écrit :
Andrew Dunstan and...@dunslane.net writes:
On 05/16/2013 05:41 AM, Dimitri Fontaine wrote:
And VPATH building of extension is crucially important for me, as the
easiest
Jon Nelson escribió:
Am I doing this the right way? Should I be posting the full patch each
time, or incremental patches?
Full patch each time is okay. Context-format patch is even better.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support,
On Fri, May 17, 2013 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andres Freund and...@2ndquadrant.com writes:
On 2013-05-17 01:29:25 +0900, Amit Langote wrote:
Can this stay in the future releases for new users of libpq to
consider using it (saving them a reconnection, however small a
On Wed, May 15, 2013 at 8:24 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I've been thinking for a while that we need some other system for
managing other kinds of invalidations. For example, suppose we want
to cache relation sizes in blocks. So we
Robert Haas robertmh...@gmail.com writes:
2. If you don't find an entry for your target rel in the cache, aren't
you still going to have to do an lseek?
Don't think of it as a cache. The caching happens inside each
backend's relcache; the shared memory structure is just a tool to
force
On May 16, 2013, at 7:02 AM, Dimitri Fontaine dimi...@2ndquadrant.fr wrote:
I find this feature quite useful, but I understand that my use case
may be quite unique.
Just to say that I too find what you've done quite useful. Please add
your patch to the next commit fest for consideration in
On Thu, May 16, 2013 at 1:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
2. If you don't find an entry for your target rel in the cache, aren't
you still going to have to do an lseek?
Don't think of it as a cache. The caching happens inside each
Alvaro Herrera alvhe...@2ndquadrant.com writes:
Then there's the outright weird stuff using ancient makefiles ..
*grumble* pg_filedump *grumble*
I've never made any effort to improve the original makefile for that.
Want to send a patch?
regards, tom lane
--
Sent via
Tom Lane wrote:
Alvaro Herrera alvhe...@2ndquadrant.com writes:
Then there's the outright weird stuff using ancient makefiles ..
*grumble* pg_filedump *grumble*
I've never made any effort to improve the original makefile for that.
Want to send a patch?
Not right away, but I will get to
On 05/16/2013 12:16 PM, Timothy Garnett wrote:
I think you'd have to be real careful around foreign key constraints
for that to work.
Not especially. All you need to do is bootstrap the database with a
bunch of empty table targets (no constraints, keys, etc), then restore
with the xargs
If you need something like this short term, we actually found a way to do it
ourselves for a migration we performed back in October. The secret is xargs
with the -P option:
xargs -I{} -P 8 -a table-list.txt \
bash -c pg_dump -Fc -t {} my_db | pg_restore -h remote -d my_db
Fill
I'll try to get the primary upgraded over the weekend when we can afford a
restart.
In the meantime I have a single test showing that a shutdown, snapshot,
restart produces a backup that passes the vacuum analyze test. I'm going
to run a full vacuum today.
-David
On Wed, May 15, 2013 at 3:53
On Wed, May 15, 2013 at 6:40 PM, Peter Geoghegan p...@heroku.com wrote:
On Wed, May 15, 2013 at 3:46 AM, Robert Haas robertmh...@gmail.com wrote:
One possible objection to this line of attack is that, IIUC, waits to
acquire a LWLock are non-interruptible. If someone tells PostgreSQL
to wait
On Thu, May 16, 2013 at 11:16 AM, Robert Haas robertmh...@gmail.com wrote:
Well, I think it IS a Postgres precept that interrupts should get a
timely response. You don't have to agree, but I think that's
important.
Well, yes, but the fact of the matter is that it is taking high single
digit
Hi,
I've just started 9.3 beta testing and I noticed that a simple view
defined on top of a writable foreign table is not automatically
updatable.
Given that these are both new-to-9.3 features, I think it would be a
shame if they don't work together. It's basically a 1-line patch to
make such
Dean Rasheed dean.a.rash...@gmail.com writes:
I've just started 9.3 beta testing and I noticed that a simple view
defined on top of a writable foreign table is not automatically
updatable.
Given that these are both new-to-9.3 features, I think it would be a
shame if they don't work together.
On 05/16/2013 05:16 PM, Tom Lane wrote:
Dean Rasheed dean.a.rash...@gmail.com writes:
I've just started 9.3 beta testing and I noticed that a simple view
defined on top of a writable foreign table is not automatically
updatable.
Given that these are both new-to-9.3 features, I think it would
On 16 May 2013 22:16, Tom Lane t...@sss.pgh.pa.us wrote:
This is assuming that an FDW that defines, say, ExecForeignDelete
is thereby promising that *all* tables it supports are deletable. That
is not required by the current FDW API spec.
Ah OK, I didn't appreciate that distinction.
If we
Hi all,
I've downloaded PLJava, the latest version, which doesn't seem to have a binary
distribution at all for 9.2, so I'm trying to build it from the source for
Postgres 9.2. I have the DB itself installed on Windows 7 64 bit as a binary
install. I've had to do a fair bit of hacking with the
On Thu, May 16, 2013 at 08:38:59PM +0530, Amit Kapila wrote:
I usually mention items that have a user-visible change, or are easy to
explain, or apply to most queries. I am not sure this falls into any
of
those categories.
Can you suggest some release note text for this item?
I
'Bruce Momjian' br...@momjian.us writes:
On Thu, May 16, 2013 at 08:38:59PM +0530, Amit Kapila wrote:
Reduce query processing overhead by avoiding insertion of useless plan nodes
OR
Improve performance of certain kind of queries by avoiding extra processing
of doing projection
This applies
On Thu, May 16, 2013 at 06:49:33PM -0400, Tom Lane wrote:
'Bruce Momjian' br...@momjian.us writes:
On Thu, May 16, 2013 at 08:38:59PM +0530, Amit Kapila wrote:
Reduce query processing overhead by avoiding insertion of useless plan
nodes
OR
Improve performance of certain kind of queries
On 05/16/2013 05:59 PM, Paul Hammond wrote:
Hi all,
I've downloaded PLJava, the latest version, which doesn't seem to have
a binary distribution at all for 9.2, so I'm trying to build it from
the source for Postgres 9.2. I have the DB itself installed on Windows
7 64 bit as a binary
On 5/16/13 9:16 AM, Jon Nelson wrote:
Am I doing this the right way? Should I be posting the full patch each
time, or incremental patches?
There are guidelines for getting your patch in the right format at
https://wiki.postgresql.org/wiki/Working_with_Git#Context_diffs_with_Git
that would
On Wed, May 15, 2013 at 8:54 PM, Stephen Frost sfr...@snowman.net wrote:
Starting a new thread to avoid hijacking Heikki's original, but..
* Heikki Linnakangas (hlinnakan...@vmware.com) wrote:
Truncating a heap at the end of vacuum, to release unused space back to
the OS, currently requires
On Tue, May 14, 2013 at 3:52 PM, Kevin Grittner kgri...@ymail.com wrote:
We could drive the triggering of incremental maintenance off of the
dependency information which is already stored, but for performance
we probably want to add a new pg_class flag to indicate that the
relation is
On Thu, May 16, 2013 at 11:55 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I've not really reviewed fd.c for other instances of the same bug,
but I do see some places where there are DO_DB(...) debug calls in
places where errno had better not change. I'm thinking maybe we should
improve that macro
On Thu, May 16, 2013 at 7:01 AM, Andres Freund and...@2ndquadrant.com wrote:
I unfortunately have to say I don't really see the point of this. The
cost of the additional connection attempt is rather low and we have to
deal with the superflous attempts anyway since there will be old libpqs
Hello,
I have observed the following same situation in PG 9.3beta1
Multiple PSQL clients are connected to server, some of them running
transaction and some of them are idle state.
When one of the backend is killed or crashed (using kill -9 backend-pid).
The connection reset attempt from the
Robert Haas robertmh...@gmail.com wrote:
Kevin Grittner kgri...@ymail.com wrote:
We could drive the triggering of incremental maintenance off of the
dependency information which is already stored, but for performance
we probably want to add a new pg_class flag to indicate that the
relation is
On Thu, May 16, 2013 at 2:42 PM, Peter Geoghegan p...@heroku.com wrote:
On Thu, May 16, 2013 at 11:16 AM, Robert Haas robertmh...@gmail.com wrote:
Well, I think it IS a Postgres precept that interrupts should get a
timely response. You don't have to agree, but I think that's
important.
-- Forwarded message --
From: Liming Hu dawnin...@gmail.com
Date: Thu, May 16, 2013 at 5:41 PM
Subject: request a new feature in fuzzystrmatch
To: pgsql-hackers@postgresql.org
Hi,
I am studying your levenshtein edit distance contribution in Postgresql.
Can we add
Robert,
For not understanding me, we seem to be in violent agreement. ;)
* Robert Haas (robertmh...@gmail.com) wrote:
I think you might be confused, or else I'm confused, because I don't
believe we have any such thing as an extent lock.
The relation extension lock is what I was referring
On Thu, May 16, 2013 at 8:33 PM, Kevin Grittner kgri...@ymail.com wrote:
Robert Haas robertmh...@gmail.com wrote:
Kevin Grittner kgri...@ymail.com wrote:
We could drive the triggering of incremental maintenance off of the
dependency information which is already stored, but for performance
we
On Thu, May 16, 2013 at 5:43 PM, Robert Haas robertmh...@gmail.com wrote:
At times, like when the system is under really heavy load? Or at
times, like depending on what the backend is doing? We can't do a
whole lot about the fact that it's possible to beat a system to death
so that, at the
On Thu, May 16, 2013 at 5:43 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, May 16, 2013 at 2:42 PM, Peter Geoghegan p...@heroku.com wrote:
On Thu, May 16, 2013 at 11:16 AM, Robert Haas robertmh...@gmail.com wrote:
Well, I think it IS a Postgres precept that interrupts should get a
68 matches
Mail list logo
