Rod Taylor wrote:
On Fri, Feb 25, 2011 at 14:26, Alvaro Herrera
alvhe...@commandprompt.comwrote:
Excerpts from Rod Taylor's message of vie feb 25 14:03:58 -0300 2011:
How practical would it be for analyze to keep a record of response times
for
given sections of a table as it
Grzegorz Jaskiewicz wrote:
On 25 Feb 2011, at 13:18, Robert Haas wrote:
People coming from Oracle are not favorably
impressed either by the amount of monitoring data PostgreSQL can
gather or by the number of knobs that are available to fix problems
when they occur. We don't need to
Robert Haas wrote:
On Sat, Feb 26, 2011 at 1:57 AM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
Actually, we *do* have some idea which tables are hot. ?Or at least, we
could. ? Currently, pg_stats for tables are timeless; they just
accumulate from the last reset, which has
Brendan Jurd wrote:
On 26 February 2011 18:06, Bruce Momjian br...@momjian.us wrote:
Any progress on this?
I ended up doing most of the work, but never got around to finishing
it off. Thanks for the reminder, though. I'll get that one ready and
drop it onto the next CF.
Added to
On Sun, Feb 27, 2011 at 01:21, Josh Kupershmidt schmi...@gmail.com wrote:
Hi all,
I noticed an off by one error in psql's verbose-mode display for \dg
and \du. In verbose mode, \dg and \du will not display the
Replication attribute:
test=# \dg rep
List of roles
Role name |
On 23.02.2011 03:00, Joachim Wieland wrote:
On Tue, Feb 22, 2011 at 3:34 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Yes, that's the point I was trying to make. I believe the idea of a hash was
that it takes less memory than storing the whole snapshot (and more
On 2011-02-26 20:59, Magnus Hagander wrote:
On Sat, Feb 26, 2011 at 20:48, Yeb Havingayebhavi...@gmail.com wrote:
On 2011-02-26 18:19, Magnus Hagander wrote:
Attached is an updated version of the patch that includes these
changes, as well as Windows support and an initial cut at a ref page
Anton antonin.hou...@gmail.com writes:
I've been playing with 'native XML' for a while and now wondering if
further development of such a feature makes sense for Postgres.
...
Unlike 'libxml2', the parser uses palloc()/pfree(). The output format is
independent from any 3rd party code.
Hmm,
On 2011-02-24 6:40 PM, I wrote:
I am planning on working on the documentation this weekend.
And here's my attempt. The language is a bit poor at some places but I
can't think of anything better.
I tried to be more strict about using subquery when talking about
WITHs in general since
I have applied a patch to improve shared memory failure reporting,
attached. We no longer report actual parameter _values_ and suggest
that other parameters might also cause such failures.
---
Alvaro Herrera wrote:
On Sun, Feb 27, 2011 at 3:01 AM, Bruce Momjian br...@momjian.us wrote:
Grzegorz Jaskiewicz wrote:
On 25 Feb 2011, at 13:18, Robert Haas wrote:
People coming from Oracle are not favorably
impressed either by the amount of monitoring data PostgreSQL can
gather or by the number of knobs
On Sun, Feb 27, 2011 at 3:03 AM, Bruce Momjian br...@momjian.us wrote:
You make it sound as if we know how but are just too lazy to right the
code. That is not one of the weaknesses that this community has.
Well, several automatic idea have been floated, but rejected because
they don't work
I wrote:
I'm inclined to think that it would be best to move the responsibility
for calling AfterTriggerBeginQuery/AfterTriggerEndQuery into the
executor. That would get us down to
CreateQueryDesc(...);
ExecutorStart(...); // now includes AfterTriggerBeginQuery
Marko Tiikkaja marko.tiikk...@cs.helsinki.fi writes:
On 2011-02-24 6:40 PM, I wrote:
I am planning on working on the documentation this weekend.
And here's my attempt. The language is a bit poor at some places but I
can't think of anything better.
Thanks, will work on this next.
On 02/27/2011 10:45 AM, Tom Lane wrote:
Antonantonin.hou...@gmail.com writes:
I've been playing with 'native XML' for a while and now wondering if
further development of such a feature makes sense for Postgres.
...
Unlike 'libxml2', the parser uses palloc()/pfree(). The output format is
Committed.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Andrew Dunstan and...@dunslane.net writes:
On 02/27/2011 10:45 AM, Tom Lane wrote:
Hmm, so this doesn't rely on libxml2 at all? Given the amount of pain
that library has caused us, getting out from under it seems like a
mighty attractive idea. How big a chunk of code do you think it'd be
by
On Feb 27, 2011, at 11:23 AM, Tom Lane wrote:
Well, that's why I asked --- if it's going to be a huge chunk of code,
then I agree this is the wrong path to pursue. However, I do feel that
libxml pretty well sucks, so if we could replace it with a relatively
small amount of code, that might
David E. Wheeler da...@kineticode.com writes:
On Feb 27, 2011, at 11:23 AM, Tom Lane wrote:
No, because the xpath stuff is fundamentally broken, and nobody seems to
know how to make libxslt do what we actually need. See the open bugs
on the TODO list.
XPath is broken? I use it heavily in
On 27/02/11 19:37, David E. Wheeler wrote:
On Feb 27, 2011, at 11:23 AM, Tom Lane wrote:
Well, that's why I asked --- if it's going to be a huge chunk of code,
then I agree this is the wrong path to pursue. However, I do feel that
libxml pretty well sucks, so if we could replace it with a
On Feb 27, 2011, at 11:43 AM, Tom Lane wrote:
XPath is broken? I use it heavily in the Perl module Test::XPath and now, in
PostgreSQL, with my explanation extension.
Well, if you're only using cases that work, you don't need to worry.
Okay then.
David
--
Sent via pgsql-hackers mailing
Mike Fowler m...@mlfowler.com writes:
I don't believe that XPath is fundamentally broken, but I think Tom
may have meant xslt. When reviewing a recent patch to xml2/xslt I found
a few bugs in the way were using libxslt, as well as a bug in the
library itself (see
From what I have checked, all work on making postgresql compile on new
platforms should be posted to this list, so here it goes.
The attached patch (also available at
http://www.rumko.net/0001-DragonFly-BSD-support.patch ) applies cleanly to the
master branch and can be cherry-picked to
On Mon, Feb 14, 2011 at 8:58 AM, Anssi Kääriäinen
anssi.kaariai...@thl.fi wrote:
On 02/14/2011 02:10 PM, Torello Querci wrote:
I suppose that give the right to the owner db user to terminate or
cancel other session connected to the database which it is owner is a
good thing.
I not see any
On Sun, Feb 27, 2011 at 06:44:32PM +, Tom Lane wrote:
Refactor the executor's API to support data-modifying CTEs better.
Should something about this go into the release notes?
Cheers,
David.
--
David Fetter da...@fetter.org http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666
Le 18 févr. 2011 à 08:26, Tom Lane a écrit :
=?iso-8859-1?Q?R=E9mi_Zara?= remi_z...@mac.com writes:
Le 12 févr. 2011 à 18:51, Peter Eisentraut a écrit :
It's only failing on this one machine, but there isn't anything
platform-specific in this code, so I'd look for memory management faults
I think there would be value in giving the DBA an easier way to see
which tables are hot, but I am really leery about the idea of trying
to feed that directly into the query planner. I think this is one of
those cases where we let people tune it manually for starters, and
then wait for
Sorry for resending, I forgot to add 'pgsql-hackers' to CC.
Original Message
Subject:Re: [HACKERS] Native XML
Date: Sun, 27 Feb 2011 23:18:03 +0100
From: Anton antonin.hou...@gmail.com
To: Tom Lane t...@sss.pgh.pa.us
On 02/27/2011 04:45 PM, Tom Lane wrote:
Added to TODO:
Allow simpler reporting of the unix domain socket directory and allow
easier configuration of its default location
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg01555.php
Folks,
Sarah and I are fine, having missed out on the disaster, but
Christchurch could use some help.
http://www.christchurchearthquakeappeal.govt.nz/
http://www.redcross.org.nz/donate
Cheers,
David.
--
David Fetter da...@fetter.org http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666
On sön, 2011-02-27 at 21:19 +0100, Rumko wrote:
The attached patch (also available at
http://www.rumko.net/0001-DragonFly-BSD-support.patch ) applies cleanly to the
master branch and can be cherry-picked to REL9_0_STABLE branch without
conflicts.
It seems to me that it would be easier to just
On sön, 2011-02-27 at 10:45 -0500, Tom Lane wrote:
Hmm, so this doesn't rely on libxml2 at all? Given the amount of pain
that library has caused us, getting out from under it seems like a
mighty attractive idea.
This doesn't replace the existing xml functionality, so it won't help
getting rid
On 02/27/2011 03:06 PM, Tom Lane wrote:
Mike Fowlerm...@mlfowler.com writes:
I don't believe that XPath is fundamentally broken, but I think Tom
may have meant xslt. When reviewing a recent patch to xml2/xslt I found
a few bugs in the way were using libxslt, as well as a bug in the
library
David,
Glad to hear that!
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
Folks,
Sarah and I are fine, having missed out on the disaster, but
Christchurch could use some help.
On Sun, Feb 27, 2011 at 3:04 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Why exactly, Heikki do you think the hash is more troublesome?
It just feels wrong to rely on cryptography just to save some shared memory.
Remember that it's not only about saving shared memory, it's
Andrew Dunstan and...@dunslane.net writes:
On 02/27/2011 03:06 PM, Tom Lane wrote:
The case that I don't think we have any idea how to solve is
http://archives.postgresql.org/pgsql-hackers/2010-02/msg02424.php
I'd forgotten about this. But as ugly as it is, I don't think it's
libxml2's
On 02/27/2011 10:07 PM, Tom Lane wrote:
Andrew Dunstanand...@dunslane.net writes:
On 02/27/2011 03:06 PM, Tom Lane wrote:
The case that I don't think we have any idea how to solve is
http://archives.postgresql.org/pgsql-hackers/2010-02/msg02424.php
I'd forgotten about this. But as ugly as
On Thu, Jan 6, 2011 at 10:08 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
We could modify pg_dump to emit RESET AUTHORIZATION in --binary-upgrade
mode. I am unclear if that might cause some other problems though.
I finally figured out
Robert Treat r...@xzilla.net writes:
Did anything ever come of this discussion?
I think it's a TODO --- nothing done about it as yet, AFAIR.
On one of the databases I
was upgrading, I ran into a similar problem with roles that are set as
roles. The problem seems to stem from pg_dumpall
Marko Tiikkaja marko.tiikk...@cs.helsinki.fi writes:
On 2011-02-24 6:40 PM, I wrote:
I am planning on working on the documentation this weekend.
And here's my attempt. The language is a bit poor at some places but I
can't think of anything better.
Applied after some rather heavy
40 matches
Mail list logo
