On Tuesday, August 11, 2009, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
2009/8/11 Robert Haas robertmh...@gmail.com
We should probably have a separate discussion about what the least
committable unit would be for this patch. I wonder if it might be
sufficient to provide
2009/8/11 Pavel Stehule pavel.steh...@gmail.com:
It's nice. I am playing with it, and now I found some potential issue.
The parser is maybe too tolerant:
postgres=# select to_char(3.14323,'9.9(a');
to_char
--
3.1e+00
(1 row)
I guess we *could* add code to throw an error
On Tuesday 11 August 2009 08:28:24 Jaime Casanova wrote:
try to build the docs to see how to properly test this and seems like
you have to teach contrib.sgml and bookindex.sgml about
dict-unaccent... and when i did that i got this:
openjade -wall -wno-unused-param -wno-empty -wfully-tagged
What is hot and standby about the proposed hot standby feature?
The way I understand these terms in a replication/cluster scenario are:
cold - If the first node dies, you need to start the replacement node from a
standing start.
warm - If the first node dies, the replacement node needs to do
2009/8/11 Tom Lane t...@sss.pgh.pa.us:
Brendan Jurd dire...@gmail.com writes:
Here's version 7.
Applied with a couple of corrections: the numeric case wasn't dealing
with NaNs in the same way as the float cases,
Thanks for that.
I do think that the whole business of printing #.# is
On Monday 10 August 2009 21:53:57 Alvaro Herrera wrote:
I understand that the placement of the generated docs in the sourcedir
instead of the builddir is so that it is included in the tarball,
correct? I admit I was surprised by that change.
I did point that out upthread, with you in
Well, here is the patch. I've included a README, which I paste here.
If someone wants to play with it (after the CommitFest...) feel free to
do so.
While it was an interesting thing to try, I don't think it has enough
potential to justify more effort...
* How to test
- apply
On Mon, Aug 10, 2009 at 03:43:45PM -0400, Tom Lane wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Still, it rates pretty high on my astonishment scale that a
COALESCE of two untyped NULLs (or
On Tue, Aug 11, 2009 at 6:35 AM, Sam Masons...@samason.me.uk wrote:
On Mon, Aug 10, 2009 at 03:43:45PM -0400, Tom Lane wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Still, it rates pretty high
On Tue, Aug 11, 2009 at 5:30 AM, Peter Eisentrautpete...@gmx.net wrote:
What is hot and standby about the proposed hot standby feature?
Absolutely nothing. It's horribly misnamed.
I have also long argued that Synchronous Replication should really
be called Streaming Replication. Perhaps it
Witting a box@point function easy. Having a spot of trouble trying to
figure out where and how to graft this into the GiST stuff. Could
someone please point me in the general direction?
Thanks.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Mon, Aug 10, 2009 at 13:41, Magnus Hagandermag...@hagander.net wrote:
On Wed, Jul 22, 2009 at 17:05, Magnus Hagandermag...@hagander.net wrote:
Dave has built binaries for 8.3.7 and 8.4.0 for this, available at:
http://developer.pgadmin.org/~dpage/postgres_exe_virtualalloc-8_3.zip
Am I off? What other definition of terms justifies the description of hot
standby?
I think that Hot Standby is associated with the high WAL recovery
capacity.
In my opinion, is a good term to symbolizes the superiority compared with
Warm Standby.
--
Matheus Ricardo Espanhol
Brendan Jurd wrote:
2009/8/11 Tom Lane t...@sss.pgh.pa.us:
Brendan Jurd dire...@gmail.com writes:
Here's version 7.
Applied with a couple of corrections: the numeric case wasn't dealing
with NaNs in the same way as the float cases,
Thanks for that.
I do think that the whole
Robert Haas wrote:
On Tue, Aug 11, 2009 at 5:30 AM, Peter Eisentrautpete...@gmx.net wrote:
What is hot and standby about the proposed hot standby feature?
OK, so it is warm slave.
Absolutely nothing. It's horribly misnamed.
I have also long argued that Synchronous Replication should
have the latest docs at
http://developer.postgresql.org/pgdocs/postgres/index.html stopped
being built? It sure looks like it somehow.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Tue, Aug 11, 2009 at 14:37, Andrew Dunstanand...@dunslane.net wrote:
have the latest docs at
http://developer.postgresql.org/pgdocs/postgres/index.html stopped being
built? It sure looks like it somehow.
My guess it's designed to just uncompress the tarball, and is thus
failing. I don't
I believe out of petere's directory / crontab ..
Sent from my iPhone
On 2009-08-11, at 9:43, Magnus Hagander mag...@hagander.net wrote:
On Tue, Aug 11, 2009 at 14:37, Andrew Dunstanand...@dunslane.net
wrote:
have the latest docs at
http://developer.postgresql.org/pgdocs/postgres/index.html
Magnus Hagander wrote:
On Tue, Aug 11, 2009 at 14:37, Andrew Dunstanand...@dunslane.net wrote:
have the latest docs at
http://developer.postgresql.org/pgdocs/postgres/index.html stopped being
built? It sure looks like it somehow.
My guess it's designed to just uncompress the tarball, and is
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
Magnus Hagander wrote:
My guess it's designed to just uncompress the tarball, and is thus
failing. I don't know where those scripts are supposed to live.. Marc?
yeah pretty sure that the docs changes also broke (-HEAD) snapshot
generation
Bruce Momjian br...@momjian.us wrote:
OK, so it is warm slave.
That is technically accurate, given the preceding definitions, but it
has disturbing connotations. Enough so, in my view, to merit getting
a little more creative in the naming. How about warm replica?
Other ideas?
I agree
Hi,
Paul Matthews p...@netspace.net.au writes:
Witting a box@point function easy. Having a spot of trouble trying to
figure out where and how to graft this into the GiST stuff. Could
someone please point me in the general direction?
You want index support for it, I suppose?
Without index
Peter Eisentraut pete...@gmx.net writes:
I've been thinking that we could actually get rid of that build-in-srcdir
behavior, which also occasionally puzzles vpath users with respect to gram.c
and so on. The new behavior would be to build targets in the local
directory.
The only
On Mon, Aug 10, 2009 at 19:33, Magnus Hagandermag...@hagander.net wrote:
On Mon, Aug 10, 2009 at 16:58, Tom Lanet...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Mon, Aug 10, 2009 at 16:10, Tom Lanet...@sss.pgh.pa.us wrote:
8.2 as well, no?
8.2 has a different shmem
Hi,
On Tue, Aug 11, 2009 at 3:33 PM, Magnus Hagandermag...@hagander.net wrote:
We should probably have a separate discussion about what the least
committable unit would be for this patch. I wonder if it might be
sufficient to provide a facility for streaming WAL, plus a standalone
tool for
On Aug 11, 2009, at 5:32 AM, Bruce Momjian wrote:
OK, so it is warm slave.
I suggest steaming servant. Or tepid assistant.
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Aug 11, 2009 at 16:30, Magnus Hagandermag...@hagander.net wrote:
On Mon, Aug 10, 2009 at 19:33, Magnus Hagandermag...@hagander.net wrote:
On Mon, Aug 10, 2009 at 16:58, Tom Lanet...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Mon, Aug 10, 2009 at 16:10, Tom
Hi,
On Tue, Aug 11, 2009 at 1:25 PM, Robert Haasrobertmh...@gmail.com wrote:
But just to kick off the discussion, here is Heikki's review of Synch
Rep on 7/15:
http://archives.postgresql.org/pgsql-hackers/2009-07/msg00913.php
I think the key phrases in this review are I believe we have
On Tue, Aug 11, 2009 at 12:30:58PM +0300, Peter Eisentraut wrote:
warm - If the first node dies, the replacement node needs to do some work to
get ready, but it's a lot quicker than cold.
hot - If the first node dies, the replacement node can take over immediately.
For example, I'd say
Hello Group,
I'd like to build an extension to PostgreSQL. It will intercept
queries and perform some transformations on the query and on the data
returned, given some business rules that the users have specified.
What's the best way to do this? It seems like if I model the pgpool-
II
Robert Haas robertmh...@gmail.com writes:
On Mon, Aug 10, 2009 at 6:52 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Only if they aren't applied by then. One reason that we normally only
run pgindent at the end of the devel cycle is that that's when
(presumably) the smallest amount of patches remain
On Tue, 2009-08-11 at 08:12 -0700, David E. Wheeler wrote:
On Aug 11, 2009, at 5:32 AM, Bruce Momjian wrote:
OK, so it is warm slave.
I suggest steaming servant. Or tepid assistant.
We can't use those, I think they are on the list for Ubuntu.
Joshua D. Drake
David
--
PostgreSQL -
On Tue, Aug 11, 2009 at 08:56:38AM -0500, Kevin Grittner wrote:
Bruce Momjian br...@momjian.us wrote:
OK, so it is warm slave.
That is technically accurate, given the preceding definitions, but
it has disturbing connotations. Enough so, in my view, to merit
getting a little more
Robert Haas robertmh...@gmail.com writes:
I think I might be starting to understand what you're getting at here.
Let me check: I think what you're saying is that the Expr node is
potentially useful to clients for identifying where in the tree the
Exprs are, even without specific knowledge
On Tue, Aug 11, 2009 at 11:56 AM, Tom Lanet...@sss.pgh.pa.us wrote:
OK, I get it. Thanks for bearing with me. The theory that the
smallest amount of patches remain outstanding at that point is
probably only true if the pgindent run is done relatively soon after
the last CommitFest. In the
Robert Haas wrote:
I'm not sure there's a
good solution to this problem short of making pgindent easy enough
that we can make it a requirement for patch submission, and I'm not
sure that's practical.
But in any case, I think running pgindent immediately after the last
CommitFest rather than
Peter,
I believe we're just copying Oracle's terminology. While that
terminology is not consistent, it is understood by the industry. Oracle
defined their Hot Standby to have both asynchronous and synchronous modes:
http://www.oracle.com/technology/products/rdb/htdocs/dbms/hotstandby.html
The
On Tue, Aug 11, 2009 at 12:11 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I think I might be starting to understand what you're getting at here.
Let me check: I think what you're saying is that the Expr node is
potentially useful to clients for identifying
Is there an easier way of going about this other than replacing the
postmaster / postgres components?
I'd start with creating my own extended version to psql (the client
library), I suppose. But since I don't really know what kind of
transformations you have in mind, any advice is going to be
On Tue, Aug 11, 2009 at 1:08 PM, Josh Berkusj...@agliodbs.com wrote:
I believe we're just copying Oracle's terminology. While that
terminology is not consistent, it is understood by the industry. Oracle
defined their Hot Standby to have both asynchronous and synchronous modes:
On Tue, Aug 11, 2009 at 12:52 PM, Andrew Dunstanand...@dunslane.net wrote:
Robert Haas wrote:
I'm not sure there's a
good solution to this problem short of making pgindent easy enough
that we can make it a requirement for patch submission, and I'm not
sure that's practical.
But in any
David Fetter wrote:
On Tue, Aug 11, 2009 at 08:56:38AM -0500, Kevin Grittner wrote:
Bruce Momjian br...@momjian.us wrote:
OK, so it is warm slave.
Why isn't it just a read only slave. Do some systems
have read-only slave databases that can't serve as a warm
standby system as well as this
On Tue, 11 Aug 2009 13:11:47 -0400
Robert Haas robertmh...@gmail.com wrote:
Unfortunately, I have to admit to total confusion. The idea in the
last paragraph seems reasonable to me, but since I don't understand
the other alternative, I can't say whether it's better or worse. I
wonder if we
Mike i...@snappymail.ca writes:
Have any tool authors stepped up and committed resources to utilizing
this feature in the near term?
I don't think anyone's promised much. If you want to have a go at using
it, we'd be very happy.
I'm guessing that my vision likely exceeds the scope of this
Robert Haas wrote:
On Tue, Aug 11, 2009 at 12:52 PM, Andrew Dunstanand...@dunslane.net wrote:
Robert Haas wrote:
I'm not sure there's a
good solution to this problem short of making pgindent easy enough
that we can make it a requirement for patch submission, and I'm not
sure that's
On 08/11/2009 09:56 AM, Kevin Grittner wrote:
Bruce Momjianbr...@momjian.us wrote:
OK, so it is warm slave.
That is technically accurate, given the preceding definitions, but it
has disturbing connotations. Enough so, in my view, to merit getting
a little more creative in the
On Tue, Aug 11, 2009 at 2:48 PM, Mark Mielkem...@mark.mielke.cc wrote:
On 08/11/2009 09:56 AM, Kevin Grittner wrote:
Bruce Momjian br...@momjian.us wrote:
OK, so it is warm slave.
That is technically accurate, given the preceding definitions, but it
has disturbing connotations. Enough
Andrew Dunstan and...@dunslane.net writes:
Robert Haas wrote:
Where it really bit me as when it reindented the DATA() statements
that were touched by ALTER TABLE ... SET STATISTICS DISTINCT. It's
not so hard to compare code, but comparing DATA() lines is the pits.
Oh? Maybe that's a problem
On Tue, Aug 11, 2009 at 2:10 PM, Ron Mayerrm...@cheapcomplexdevices.com wrote:
David Fetter wrote:
On Tue, Aug 11, 2009 at 08:56:38AM -0500, Kevin Grittner wrote:
Bruce Momjian br...@momjian.us wrote:
OK, so it is warm slave.
Why isn't it just a read only slave. Do some systems
have
Andrew Dunstan escribió:
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
Robert Haas wrote:
Where it really bit me as when it reindented the DATA() statements
that were touched by ALTER TABLE ... SET STATISTICS DISTINCT. It's
not so hard to compare code, but comparing DATA()
On Aug 11, 1:11 pm, j...@agliodbs.com (Josh Berkus) wrote:
Is there an easier way of going about this other than replacing the
postmaster / postgres components?
I'd start with creating my own extended version to psql (the client
library), I suppose. But since I don't really know what kind
On 08/11/2009 02:52 PM, Robert Haas wrote:
On Tue, Aug 11, 2009 at 2:48 PM, Mark Mielkem...@mark.mielke.cc wrote:
I remember this debate from 6 months ago. :-)
I prefer not to try and fit square pegs into round holes. Streaming
replication sounds like the best description. It may not be
Mark Mielke escribió:
I don't think I was confused before - but I am confused now. :-)
This patch does not provide streaming replication?
No. What it does is allow you to query the slave while it's still
replaying transactions. There's another patch allowing you to do
stream replication.
Mark Mielke m...@mark.mielke.cc wrote:
This patch does not provide streaming replication?
There's a separate effort to provide asynchronous and synchronous
streaming replication. Different patch.
Hot standby to me means the slave is as close to up-to-date as
possible and can potentially
Alvaro Herrera alvhe...@commandprompt.com writes:
Andrew Dunstan escribió:
Here's the extract attached. I replace tabs with a literal '\t' so
I could see what it was doing. I can't make much head or tail of it
either.
pgindent uses entab/detab, which counts spaces and replaces them with
Tom Lane wrote:
Mike i...@snappymail.ca writes:
Have any tool authors stepped up and committed resources to utilizing
this feature in the near term?
I don't think anyone's promised much. If you want to have a go at using
it, we'd be very happy.
I'm guessing that my vision
Matt Culbreth mattculbr...@gmail.com wrote:
My new component intercepts this, and decides if it wants to do
something
If it does, it passes the request over to my new server (via
sockets), does its work, and pass back the results
That's still too vague to allow people to give very
All,
So really, the streaming replication patch should be called hot
standby, and the hot standby patch should be called read only slaves?
And *why* can't we call it log-based replication?
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list
On Tue, Aug 11, 2009 at 4:07 PM, Josh Berkusj...@agliodbs.com wrote:
All,
So really, the streaming replication patch should be called hot
standby, and the hot standby patch should be called read only slaves?
And *why* can't we call it log-based replication?
+1
*) it _is_ used to replicate
On Sunday 28 June 2009 21:21:35 Robert Haas wrote:
I think that our dependencies for generated header files (gram.h,
fmgroids.h, probes.h) are not as good as they could be. What we do
right now is make src/backend/Makefile rebuild these before recursing
through its subdirectories. This works
On Tuesday 11 August 2009 21:59:48 Andrew Dunstan wrote:
Tom Lane wrote:
Mike i...@snappymail.ca writes:
Have any tool authors stepped up and committed resources to utilizing
this feature in the near term?
I don't think anyone's promised much. If you want to have a go at using
it,
On Tuesday 30 June 2009 06:59:51 Robert Haas wrote:
The attached patch merges all of the logic currently in genbki.sh and
Gen_fmgrtab.{sh,pl} into a single script called gen_catalog.pl
I can't really convince myself to like this change. I think there is some
merit that these scripts are
On Tuesday 11 August 2009 17:02:01 Tom Lane wrote:
Having all the derived files in the build directory definitely seems
to me to reduce the complexity and surprise factor, so +1 for changing.
I've looked at that briefly, and it's a bit more complicated than it would
appear. I will figure this
On Tue, Aug 11, 2009 at 01:14:56PM -0400, Robert Haas wrote:
On Tue, Aug 11, 2009 at 1:08 PM, Josh Berkusj...@agliodbs.com wrote:
I believe we're just copying Oracle's terminology. While that
terminology is not consistent, it is understood by the industry. Oracle
defined their Hot Standby
On Tuesday 11 August 2009 18:16:04 Gianni Ciolli wrote:
As for warm/hot, it depends on what you exactly mean with get
ready:
(A) If you mean it is possible to connect to the second node, then
Simon's patch is hot.
Yeah, but by that definiton doing a pg_dump/pg_restore every hour is also
On Tue, Aug 11, 2009 at 4:07 PM, Josh Berkusj...@agliodbs.com wrote:
So really, the streaming replication patch should be called hot
standby,
No. AIUI, hot standby means that when your primary falls over, the
secondary automatically promotes itself and takes over. It requires
things like
Peter Eisentraut escribió:
On Tuesday 30 June 2009 06:59:51 Robert Haas wrote:
The attached patch merges all of the logic currently in genbki.sh and
Gen_fmgrtab.{sh,pl} into a single script called gen_catalog.pl
I can't really convince myself to like this change. I think there is some
On Tue, Aug 11, 2009 at 4:52 PM, Peter Eisentrautpete...@gmx.net wrote:
On Tuesday 30 June 2009 06:59:51 Robert Haas wrote:
The attached patch merges all of the logic currently in genbki.sh and
Gen_fmgrtab.{sh,pl} into a single script called gen_catalog.pl
I can't really convince myself to
Hi,
Le 11 août 09 à 07:50, Heikki Linnakangas a écrit :
2009/8/11 Robert Haas robertmh...@gmail.com
We should probably have a separate discussion about what the least
committable unit would be for this patch. I wonder if it might be
sufficient to provide a facility for streaming WAL, plus a
Incidentally, we billed pg_dump as hot backup at some point.
mysql calls mysqlhotcopy a script that locks and flushes all tables,
then makes a copy of the database directory (all queries being locked out
while this is in progress, of course).
--
Sent via pgsql-hackers mailing list
On Tue, Aug 11, 2009 at 4:38 PM, Peter Eisentrautpete...@gmx.net wrote:
On Sunday 28 June 2009 21:21:35 Robert Haas wrote:
I think that our dependencies for generated header files (gram.h,
fmgroids.h, probes.h) are not as good as they could be. What we do
right now is make
On Tue, Aug 11, 2009 at 5:20 PM, Dimitri Fontainedfonta...@hi-media.com wrote:
We should somehow provide a default archive and restore command integrated
into the main product, so that it's as easy as turning it 'on' in the
configuration for users to have something trustworthy: PostgreSQL will
On Tue, Aug 11, 2009 at 4:00 PM, Kevin
Grittnerkevin.gritt...@wicourts.gov wrote:
Matt Culbreth mattculbr...@gmail.com wrote:
My new component intercepts this, and decides if it wants to do
something
If it does, it passes the request over to my new server (via
sockets), does its work, and
On Tue, Aug 11, 2009 at 3:59 PM, Andrew Dunstanand...@dunslane.net wrote:
Good. I had a look at this for a little while yesterday. I built it, did an
install, loaded auto_explain and then ran the regression tests. I didn't
like the output much. It looks like the XML has been dumbed down to fit
Le 11 août 09 à 23:30, Robert Haas a écrit :
On Tue, Aug 11, 2009 at 5:20 PM, Dimitri Fontainedfonta...@hi-media.com
wrote:
We should somehow provide a default archive and restore command
integrated
into the main product, so that it's as easy as turning it 'on' in the
configuration for
On Monday 10 August 2009 23:03:12 Alvaro Herrera wrote:
Hmm, I notice that this rule to install manpages is pretty slow:
for file in /pgsql/source/00head/doc/src/sgml/man1/*.1
/pgsql/source/00head/doc/src/sgml/man3/*.3
/pgsql/source/00head/doc/src/sgml/man7/*.7; do /bin/sh
Robert Haas robertmh...@gmail.com wrote:
Andrew Dunstanand...@dunslane.net wrote:
find it more tiresome to read. In effect we are swapping horizontal
expansion for vertical expansion. It would be nicer to be able to
fit a plan into a screen.
Isn't that what text format is for?
In my
On Tue, 2009-08-11 at 17:30 -0400, Robert Haas wrote:
On Tue, Aug 11, 2009 at 5:20 PM, Dimitri Fontainedfonta...@hi-media.com
wrote:
We should somehow provide a default archive and restore command integrated
into the main product, so that it's as easy as turning it 'on' in the
Robert Haas escribió:
*shrug* You don't have to accept the patch, but I'm unclear as to how
make from a subdirectory will ever work reliably without something
like this. The problem occurs when .c files have dependencies on
files that are generated by a Makefile in some other subdirectory.
On Tue, Aug 11, 2009 at 5:40 PM, Dimitri Fontainedfonta...@hi-media.com wrote:
Le 11 août 09 à 23:30, Robert Haas a écrit :
On Tue, Aug 11, 2009 at 5:20 PM, Dimitri Fontainedfonta...@hi-media.com
wrote:
We should somehow provide a default archive and restore command
integrated
into the
Robert Haas wrote:
On Tue, Aug 11, 2009 at 3:59 PM, Andrew Dunstanand...@dunslane.net wrote:
Good. I had a look at this for a little while yesterday. I built it, did an
install, loaded auto_explain and then ran the regression tests. I didn't
like the output much. It looks like the XML has
Pierre Frédéric Caillaud wrote:
Incidentally, we billed pg_dump as hot backup at some point.
mysql calls mysqlhotcopy a script that locks and flushes all tables,
then makes a copy of the database directory (all queries being locked
out while this is in progress, of course).
Doesn't
Peter Eisentraut wrote:
On Monday 10 August 2009 23:03:12 Alvaro Herrera wrote:
Hmm, I notice that this rule to install manpages is pretty slow:
Yeah, that was really freakishly complicated. Fixed now.
It is much better now, thanks.
--
Alvaro Herrera
Incidentally, we billed pg_dump as hot backup at some point.
It *is* hot backup as in taken while the database is running and fully
accessible.
mysql calls mysqlhotcopy a script that locks and flushes all tables,
then makes a copy of the database directory (all queries being locked
out
Hi,
There's a longstanding TODO item, in subject. Previous discussion was
here:
http://archives.postgresql.org/pgsql-hackers/2006-09/msg02341.php
In looking what it would take to implement it, I find that it is
trivial. The only part that looks complex is the UI for it. Is anyone
interested
On Monday 10 August 2009 18:59:51 Tom Lane wrote:
After doing make then make distclean in doc/src/sgml, I see the
following undesirable files left behind:
-rw-rw-r-- 1 tgl tgl 58 Aug 10 11:51 version.sgml
-rw-rw-r-- 1 tgl tgl 38548 Aug 10 11:51 features-unsupported.sgml
-rw-rw-r-- 1 tgl
OK, since there was no clear consensus or volunteer for preparing release
notes for alpha 1, I have started something. Let me know what you think.
(reStructuredText, if you want to play around)
.. -*- mode: rst -*-
=
Release 8.5alpha1
=
.. last commit: Simplify
Folks,
While trying unsuccessfully to help someone in IRC, they pointed me to
this:
http://www.flexiguided.de/publications.pgcollkey.en.html
Is anybody working with the kind people of FlexiGuided GmbH to see
about integrating this feature more tightly with PostgreSQL?
If not, how would we make
On Wed, Aug 12, 2009 at 12:11:28AM +0300, Peter Eisentraut wrote:
On Tuesday 11 August 2009 18:16:04 Gianni Ciolli wrote:
As for warm/hot, it depends on what you exactly mean with get
ready:
(A) If you mean it is possible to connect to the second node, then
Simon's patch is hot.
Dimitri Fontaine wrote:
Paul Matthews p...@netspace.net.au writes:
Witting a box@point function easy. Having a spot of trouble trying to
figure out where and how to graft this into the GiST stuff. Could
someone please point me in the general direction?
You want index
Tom Lane wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Andrew Dunstan escribi?:
Here's the extract attached. I replace tabs with a literal '\t' so
I could see what it was doing. I can't make much head or tail of it
either.
pgindent uses entab/detab, which counts spaces and
In the discussion of bug #4919 I wrote:
In some sense this is a bootstrap problem: what does it take to get to
the point of being able to read pg_database and its indexes? That is
necessarily not dependent on the particular database we want to join.
Maybe we could solve it by having the
A Dimecres, 12 d'agost de 2009, Peter Eisentraut va escriure:
OK, since there was no clear consensus or volunteer for preparing release
notes for alpha 1, I have started something. Let me know what you think.
(reStructuredText, if you want to play around)
Maybe I'd be interesting to add
Alvaro Herrera wrote:
Andrew Dunstan escribi?:
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
Robert Haas wrote:
Where it really bit me as when it reindented the DATA() statements
that were touched by ALTER TABLE ... SET STATISTICS DISTINCT. It's
not so hard to
On Tuesday 11 August 2009 15:37:42 Andrew Dunstan wrote:
have the latest docs at
http://developer.postgresql.org/pgdocs/postgres/index.html stopped
being built? It sure looks like it somehow.
Fixed
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Tom Lane wrote:
I'd also like to look into getting rid of the pg_auth flat file.
That would be sad for many users of pgbouncer.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Robert Haas wrote:
On Tue, Aug 11, 2009 at 4:07 PM, Josh Berkusj...@agliodbs.com wrote:
So really, the streaming replication patch should be called hot
standby,
No. AIUI, hot standby means that when your primary falls over, the
secondary automatically promotes itself and takes over. It
On Tue, Aug 11, 2009 at 4:56 PM, Tom Lanet...@sss.pgh.pa.us wrote:
A more aggressive approach would be to run pgindent immediately after
the close of *each* commitfest, but that would tend to break patches
that had gotten punted to the next fest.
What would happen if we ran pgindent
If I didn't read this email I would still be trying to figure out how
to use the explain XML patch. Thanks Albert.
I found the syntax for the explain xml format to be quite difficult to
understand at first, it would be nice to give an example or two, ie:
EXPLAIN (ANALYZE, FORMAT XML) SELECT *
Mike wrote:
The thing that caused me the most trouble was that the , wasn't very
noticeable sitting near the end of this line:
EXPLAIN [ ( { ANALYZE boolean | VERBOSE boolean | COSTS boolean |
FORMAT { TEXT | XML | JSON } } [, ...] ) ] statement
It may just be me, but I read that as the
1 - 100 of 135 matches
Mail list logo
