On Oct24, 2011, at 01:27 , Simon Riggs wrote:
FATAL: could not access status of transaction 21110784
which, in pg_subtrans, is the first xid on a new subtrans page. So we
have missed zeroing a page.
pg_control shows ... Latest checkpoint's oldestActiveXID: 2111
which shows quite
On Oct23, 2011, at 22:48 , Daniel Farina wrote:
It doesn't seem meaningful for StartupCLOG (or, indeed, any of the
hot-standby path functionality) to be called before that code is
executed, but it is anyway right now.
I think the idea is to check that the CLOG part which recovery *won't*
On 19 October 2011 05:20, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Eisentraut pete...@gmx.net writes:
I wouldn't add extra special checks for that. It might not be
completely unreasonable to have a standby that no one can connect to,
for example.
Well, you couldn't monitor its state then,
On Mon, Oct 24, 2011 at 10:05 AM, Tom Lane t...@sss.pgh.pa.us wrote:
as it seems to me that any
client that is paranoid enough to care about sync rep had better
already be handling the case of a connection loss during commit.
Agreed, but that is a problem that by definition we can't help
On Mon, Oct 24, 2011 at 16:12, Jaime Casanova ja...@2ndquadrant.com wrote:
On Mon, Oct 24, 2011 at 7:40 AM, Magnus Hagander mag...@hagander.net wrote:
synchronous_standby_names='*' is prone to such confusion in general, but it
seems that it's particularly surprising if a running pg_basebackup
Hi!
On Mon, Oct 17, 2011 at 12:38 PM, Jeff Davis pg...@j-davis.com wrote:
I started implementing subtype_diff, and I noticed that it requires
defining an extra function for each range type. Previously, the numeric
types could just use a cast, which was convenient for user-defined range
On Mon, Sep 12, 2011 at 11:53 AM, Alexey Klyukin
al...@commandprompt.com wrote:
This works in 9.1, but not in HEAD:
CREATE TABLE parent(id INTEGER, CONSTRAINT id_check CHECK(id1));
CREATE TABLE child() INHERITS(parent);
ALTER TABLE ONLY parent DROP CONSTRAINT id_check;
I'm getting:
ERROR:
On Fri, Sep 23, 2011 at 4:05 PM, Dan McGee d...@archlinux.org wrote:
On Fri, Sep 23, 2011 at 2:49 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Sep 19, 2011 at 4:36 PM, Dan McGee d...@archlinux.org wrote:
[ patch ]
I suppose it's Tom who really needs to comment on this, but I'm not
On 24.10.2011 15:29, Fujii Masao wrote:
+listitem
+ para
+ Copy the pg_control file from the cluster directory to the global
+ sub-directory of the backup. For example:
+ programlisting
+ cp $PGDATA/global/pg_control /mnt/server/backupdir/global
+ /programlisting
+ /para
+
On Sun, Oct 23, 2011 at 6:34 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Well, there is a general problem that anything which throws an ERROR
too late in the commit path is Evil; and sync rep makes that worse to
the extent that it adds more stuff late in
On 24.10.2011 15:29, Fujii Masao wrote:
In your patch, FPW is always WAL-logged at startup even when FPW has
not been changed since last shutdown. I don't think that's required.
I changed the recovery code so that it keeps track of last FPW indicated
by WAL record. Then, at end of startup, if
On Mon, Oct 24, 2011 at 4:57 AM, Omar Bettin
o.bet...@informaticaindustriale.it wrote:
I have tried 9.1.1 win64 version and when I am trying to declare a cursor
for a very large view (lot of joins and aggregate functions),
postgres is using around 3GB of memory and the query never returns.
...sorry guys...
was a misconfiguration of database.
9.1.1 is working good.
is ~4% faster than 9.0.5 for same query.
Thanks a lot.
Regards
-Messaggio originale-
Da: Pavel Stehule [mailto:pavel.steh...@gmail.com]
Inviato: lunedì 24 ottobre 2011 12:13
A: Omar Bettin
Cc:
On Mon, Oct 24, 2011 at 10:25 AM, Euler Taveira de Oliveira
eu...@timbira.com wrote:
On 24-10-2011 10:57, Robert Haas wrote:
I think the main reason why vacuumlo is a contrib module rather than
in core is that it is just a heuristic, and it might not be what
everyone wants to do. You could
Hi Tom,
...are about two hours I am trying to communicate that the problem has been
solved, but I do not see the messages in the mailing list...
Anyway,
the problems was a bad installation of database (pgsql functions).
9.1.1 is working good.
is 4% to 8% faster than 9.0.5.
Thanks a lot to
On Mon, Oct 24, 2011 at 11:33 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 24.10.2011 15:29, Fujii Masao wrote:
In your patch, FPW is always WAL-logged at startup even when FPW has
not been changed since last shutdown. I don't think that's required.
I changed the
Omar Bettin o.bet...@informaticaindustriale.it writes:
I have tried 9.1.1 win64 version and when I am trying to declare a cursor
for a very large view (lot of joins and aggregate functions),
postgres is using around 3GB of memory and the query never returns.
Could we see a self-contained test
Euler Taveira de Oliveira eu...@timbira.com writes:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it.
I'm not terribly thrilled with that because (a) large objects seem
Robert Haas robertmh...@gmail.com writes:
On Sun, Oct 23, 2011 at 6:34 PM, Tom Lane t...@sss.pgh.pa.us wrote:
BTW, it strikes me that if we want to do something about that, it ought
to be possible; but it has to be built into error handling, not a
localized hack for sync rep.
I actually
On Mon, Oct 24, 2011 at 13:46, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
+ /*
+ * Looks like an xlog file. Parse it's position.
s/it's/its/
+ */
+ if (sscanf(dirent-d_name, %08X%08X%08X, tli, log,
seg) != 3)
+
On Sun, Oct 23, 2011 at 7:01 PM, Jeff Janes jeff.ja...@gmail.com wrote:
On Fri, Oct 21, 2011 at 12:52 PM, Robert Haas robertmh...@gmail.com wrote:
Also, this line is kind of expensive:
if (!visibilitymap_test(scandesc-heapRelation,
On Mon, Oct 24, 2011 at 7:40 AM, Magnus Hagander mag...@hagander.net wrote:
synchronous_standby_names='*' is prone to such confusion in general, but it
seems that it's particularly surprising if a running pg_basebackup lets a
commit in synchronous replication to proceed. Maybe we just need a
+ /*
+* Looks like an xlog file. Parse it's position.
s/it's/its/
+*/
+ if (sscanf(dirent-d_name, %08X%08X%08X, tli, log, seg) !=
3)
+ {
+ fprintf(stderr, _(%s: could not parse xlog filename
On Mon, Oct 24, 2011 at 01:26, Tom Lane t...@sss.pgh.pa.us wrote:
Andreas Karlsson andr...@proxel.se writes:
Thanks for cleaning up the code to some sanity, I should have done so
myself when I noticed the problem.
A new version is attached.
Committed with minor adjustments --- I didn't see
On Fri, Oct 21, 2011 at 12:01 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Oct 20, 2011 at 9:51 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Oct 20, 2011 at 1:05 AM, Robert Haas robertmh...@gmail.com wrote:
OK, so this is an artifact of the changes to make libpq communication
On Mon, Oct 24, 2011 at 12:56 AM, Euler Taveira de Oliveira
eu...@timbira.com wrote:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it. While dealing with large objects
On 24/10/11 10:57, Omar Bettin wrote:
[monster query]
I see that your problem is already solved, but incidentially I'm working
on a join order planning module and I'm looking for real-life examples
of humongous queries like that to benchmark against them.
Any chance you could share the
Hi All,
I have not been able to reproduce this error, but wanted to report this
in case it might be useful.
Commit -id: 0f39d5050dc0dce99258381f33f1832c437aff85
Configure options:
--prefix=/mnt/storage/gurjeet/dev/builds//master/db --enable-debug
--enable-cassert CFLAGS=-O0
...sorry guys...
was a bad configuration of database.
9.1.1 is working good.
is 4% to 8% faster than 9.0.5.
Thanks a lot.
Regards
Omar
P.s.
attached EXPLAIN
Hmm. A 59-table join is pretty enormous
and is not the biggest, basically are delivery notes for one day seen in
vertical.
--
On Mon, Sep 26, 2011 at 10:37, Magnus Hagander mag...@hagander.net wrote:
On Sun, Sep 25, 2011 at 15:06, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 24 September 2011 11:59, Magnus Hagander mag...@hagander.net wrote:
TABLE tab completion in psql only completes to tables, not views. but
the
2011/10/24 Omar Bettin o.bet...@informaticaindustriale.it:
...sorry guys...
was a bad configuration of database.
9.1.1 is working good.
is 4% to 8% faster than 9.0.5.
Thanks a lot.
Regards
Omar
P.s.
attached EXPLAIN
attachment is missing
Pavel
Hmm. A 59-table join is pretty
Hello
please, send a result of explain analyze on 9.1.1 and older
please, use http://explain.depesz.com/
Regards
Pavel Stehule
2011/10/24 Omar Bettin o.bet...@informaticaindustriale.it:
Hello,
I have tried 9.1.1 win64 version and when I am trying to declare a cursor
for a very large
Gurjeet Singh singh.gurj...@gmail.com writes:
Starting from line 89 of terminal1.txt we see this snippet:
postgres=# rollback;
ROLLBACK
postgres=# begin TRANSACTION ;
BEGIN
postgres=# set transaction snapshot '02C8-1';
ERROR: SET TRANSACTION SNAPSHOT must be called before any
On 17.10.2011 01:09, Jeff Davis wrote:
On Sat, 2011-10-15 at 01:46 +0300, Heikki Linnakangas wrote:
* The binary i/o format includes the length of the lower and upper
bounds twice, once explicitly in range_send, and second time within the
send-function of the subtype. Seems wasteful.
Any
Excerpts from Gurjeet Singh's message of lun oct 24 13:55:44 -0300 2011:
Starting from line 89 of terminal1.txt we see this snippet:
postgres=# rollback;
ROLLBACK
postgres=# begin TRANSACTION ;
BEGIN
postgres=# set transaction snapshot '02C8-1';
ERROR: SET TRANSACTION SNAPSHOT
On 24-10-2011 10:57, Robert Haas wrote:
I think the main reason why vacuumlo is a contrib module rather than
in core is that it is just a heuristic, and it might not be what
everyone wants to do. You could store a bunch of large objects in the
database and use the returned OIDs to generate
Hi,
Since the data are of third parties, will prepare a database suitable for the
purpose.
In any case, the compressed backup will be around 20 MB.
Regards,
Omar Bettin
-Messaggio originale-
Da: Jan Urbański [mailto:wulc...@wulczer.org]
Inviato: lunedì 24 ottobre 2011 18:56
A: Omar
Robert Haas robertmh...@gmail.com writes:
[ oom_score_adj business ]
Did we do anything about this? Anyone else have an opinion on what
ought to be done?
I held off doing anything because it didn't seem like we had consensus.
OTOH, it may well be that it's not important enough to demand real
On 24-10-2011 11:36, Tom Lane wrote:
Euler Taveira de Oliveiraeu...@timbira.com writes:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it.
I'm not terribly thrilled with
On 24/10/11 19:16, Omar Bettin wrote:
Hi,
Since the data are of third parties, will prepare a database suitable for the
purpose.
In any case, the compressed backup will be around 20 MB.
If you are able to prepare a database dump that doesn't contain private
data, it would be awesome.
If
Tom Lane t...@sss.pgh.pa.us wrote:
It might be that it'd work to deal with this by reducing the
reported strength of all such cases from ERROR to WARNING. Not
sure that that's a good idea, but it might work.
Throwing an error on commit of a transaction when its work has
actually been
On 19.10.2011 17:58, Simon Riggs wrote:
On Wed, Oct 19, 2011 at 3:29 PM, Fujii Masaomasao.fu...@gmail.com wrote:
On Wed, Oct 19, 2011 at 9:45 PM, Robert Haasrobertmh...@gmail.com wrote:
I don't really see any reason to break the monitoring view just
because we did some internal refactoring.
On Mon, Oct 24, 2011 at 1:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
[ oom_score_adj business ]
Did we do anything about this? Anyone else have an opinion on what
ought to be done?
I held off doing anything because it didn't seem like we had
On 25.09.2011 16:03, Dean Rasheed wrote:
On 25 September 2011 09:43, Kohei KaiGaikai...@kaigai.gr.jp wrote:
Hi Heikki,
I checked your patch, then I have a comment and two questions here.
2011/9/14 Heikki Linnakangasheikki.linnakan...@enterprisedb.com:
Attached is a new version of the
Tom Lane t...@sss.pgh.pa.us wrote:
I had wondered whether it'd be worth optimizing that along the
lines of slot_getallattrs(). But most indexes probably have only
one column, or anyway not enough to make for a useful savings.
From a heavily-used production database:
cir= select indnatts,
On Mon, Oct 24, 2011 at 1:08 PM, Alvaro Herrera
alvhe...@commandprompt.comwrote:
Excerpts from Gurjeet Singh's message of lun oct 24 13:55:44 -0300 2011:
Starting from line 89 of terminal1.txt we see this snippet:
postgres=# rollback;
ROLLBACK
postgres=# begin TRANSACTION ;
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Tom Lane t...@sss.pgh.pa.us wrote:
I had wondered whether it'd be worth optimizing that along the
lines of slot_getallattrs(). But most indexes probably have only
one column, or anyway not enough to make for a useful savings.
From a
On Wed, October 19, 2011 15:01, Kerem Kat wrote:
Adding CORRESPONDING to Set Operations
Initial patch, filename: corresponding_clause_v2.patch
I had a quick look at the behaviour of this patch.
Btw, the examples in your email were typoed (one select is missing):
SELECT 1 a, 2 b, 3 c UNION
Tom Lane t...@sss.pgh.pa.us wrote:
Yeah, TOAST indexes are 2-column. It would be best to exclude
those from your counts, since it seems pretty unlikely that anyone
will care how fast nodeIndexonlyscan.c is for scans on toast
tables.
User indexes (excluding toast):
indnatts | count
Copy/paste problems -- the first set includes the system tables
except for toast. User tables would be the difference between the
results below. Sorry.
-Kevin
Kevin Grittner kevin.gritt...@wicourts.gov wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
Yeah, TOAST indexes are 2-column. It
On Mon, Oct 24, 2011 at 2:15 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
It doesn't look to me like the mean is above 2 (unless you have
many fewer toast tables than I suspect), so trying to optimize
many-column cases isn't going to help.
The mean is 2.4 (give or take a little
Robert Haas robertmh...@gmail.com writes:
But even though Tom's statement that most indexes are one column might
be a slight exaggeration, I suspect it probably is true that the
optimizations he's talking about for large numbers of columns won't
produce any material benefit even for a 3 or 4
On 10/24/11 12:35 PM, Tom Lane wrote:
Your point about people trying to create wider indexes to exploit
index-only scans is an interesting one, but I think it's premature to
optimize on the basis of hypotheses about what people might do in
future.
I don't think that this is hypothetical at
On Mon, Oct 24, 2011 at 3:35 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Your point about people trying to create wider indexes to exploit
index-only scans is an interesting one, but I think it's premature to
optimize on the basis of hypotheses about what people might do in
future.
Well, I don't
Josh Berkus j...@agliodbs.com wrote:
On 10/24/11 12:35 PM, Tom Lane wrote:
Your point about people trying to create wider indexes to exploit
index-only scans is an interesting one, but I think it's
premature to optimize on the basis of hypotheses about what
people might do in future.
I
Robert Haas robertmh...@gmail.com writes:
On Mon, Oct 24, 2011 at 3:35 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I wonder how trustworthy the measure of the visibilitymap_test call site
as a consumer of cycles really is.
I'm not sure either. I guess we could try short-circuiting
Hackers,
After Hekki's talk on PgConf.EU about SSI, some idea comes to my mind.
Coundn't be predicate locking implementation in SSI be used for in-database
cache invalidation.
It could be possible to implement in-database cache which will acquire
predicate locks like SSI transactions. In case of
Alexander Korotkov aekorot...@gmail.com wrote:
Coundn't be predicate locking implementation in SSI be used for
in-database cache invalidation.
It would not necessarily be limited to *in-database* caches. The
main thing would be to design a good API to the predicate locking
portion of SSI,
Tom Lane t...@sss.pgh.pa.us wrote:
I don't understand the SSI code well enough to tell if this is
sufficient or not, so I hope you guys will take a closer look at
the issue when you have time.
I will definitely give it a look. Right now we have a perfect
storm of time demands due to some
On Tue, Oct 25, 2011 at 1:46 AM, Kevin Grittner kevin.gritt...@wicourts.gov
wrote:
Alexander Korotkov aekorot...@gmail.com wrote:
Coundn't be predicate locking implementation in SSI be used for
in-database cache invalidation.
It would not necessarily be limited to *in-database* caches.
Thanks for the review!
On Tue, Oct 25, 2011 at 12:24 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 24.10.2011 15:29, Fujii Masao wrote:
+ listitem
+ para
+ Copy the pg_control file from the cluster directory to the global
+ sub-directory of the
On Mon, Oct 24, 2011 at 11:40 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
The patch looks sane, it's mostly just moving existing code around, but
there's one thing that's been bothering me about this whole idea from the
get-go:
If the bgwriter and checkpointer are two
On Tue, Oct 25, 2011 at 12:33 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
One problem with this whole FPW-tracking is that pg_lesslog makes it fail.
I'm not sure what we need to do about that - maybe just add a warning to the
docs. But it leaves a bit bad feeling in my
63 matches
Mail list logo
