On 8/27/06, Tom Lane <[EMAIL PROTECTED]> wrote:
I've applied a patch along these lines. David's plperl example now does
what (I think) he expected.
Kewl. Thanks Tom.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood
On Sun, Aug 27, 2006 at 08:49:21PM -0700, Joshua D. Drake wrote:
> AgentM wrote:
> >Sorry, but I don't get it. Why offer a closed forum for an open project?
Open source developers already send private emails, private instant
messages, or join private chat rooms.
> Because jabber is a live medium,
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
I just detected another problem with building ecpg in a VPATH
environment. This patch fixes it for me.
Can't we get some of the buildfarm machines exercising VPATH?
This kinda stuff really ought to be found immediately.
AgentM wrote:
Sorry, but I don't get it. Why offer a closed forum for an open project?
Because jabber is a live medium, unlike email. I don't want people
pinging me, out of the blue. It is the whole reason I don't use any of
the public networks. The point is for the people who are actually pa
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I just detected another problem with building ecpg in a VPATH
> environment. This patch fixes it for me.
Can't we get some of the buildfarm machines exercising VPATH?
This kinda stuff really ought to be found immediately.
regar
Alvaro Herrera wrote:
> I just detected another problem with building ecpg in a VPATH
> environment. This patch fixes it for me.
I think you will find that $(top_builddir)/$(subdir) is equivalent
to "."
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(e
Sorry, but I don't get it. Why offer a closed forum for an open project?
-M
On Aug 27, 2006, at 24:48 , Joshua D. Drake wrote:
Hello,
The community jabber server is now up. We are using the Wildfire
server from Jive Software, backed to a PostgreSQL database (of
course).
-- The idea
The idea of hooks sounds quite good to me indeed. The
issue is not PR, it's indeed pgcluster benefiting from
the maintenance of postgresql and avoiding the hassle
of having to resync its code at each postgresql
change.
I will propose something along those lines once I get
a more stable pgcluster an
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 8/24/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This reminds me of a consideration I had been intending to bring up on
>> the mailing lists: what exactly do we want to do with the SPI API for
>> RETURNING queries?
> I like adding RETURNING-specifi
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 8/27/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>> ... or the pgcluster group could check the hook list posted by the GORDA
>> project guys. In fact IIRC that patch was committed already, without
>> much discussion?
> I thought the GORDA patch
I wrote:
> I'm toying with the idea of adding a lock manager call defined as
> "give me a list of XIDs that currently hold locks conflicting with
> lockmode X on object Y" --- but not including XIDs merely waiting
> for such a lock. Then we could get the list of XIDs currently blocking
> Exclusive
On 8/27/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
... or the pgcluster group could check the hook list posted by the GORDA
project guys. In fact IIRC that patch was committed already, without
much discussion?
I thought the GORDA patch got turned down because there was no
communication betw
Peter Eisentraut wrote:
> Tom Lane wrote:
> > So I'd want to see some kind of joint proposal by multiple
> > replication projects about what hooks to add. Anybody out there want
> > to organize such a thing?
>
> Well, at least the pgcluster group could come up with a rough list of
> required ho
Gregory Stark <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> How often does that case come up in the real world, for tables that are
>> large enough that you'd care about vacuum performance?
> I would have had the same objection if it resulted in substantially more
> complex
Tom Lane wrote:
> So I'd want to see some kind of joint proposal by multiple
> replication projects about what hooks to add. Anybody out there want
> to organize such a thing?
Well, at least the pgcluster group could come up with a rough list of
required hooks, and then the other groups can jud
Tom Lane <[EMAIL PROTECTED]> writes:
> stark <[EMAIL PROTECTED]> writes:
>> There isn't really any need for the second pass in lazy vacuum if the table
>> has no indexes.
>
> How often does that case come up in the real world, for tables that are
> large enough that you'd care about vacuum perfor
Andreas Pflug <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> My take on all this is that there's no one-size-fits-all replication
>> solution, and therefore the right approach is to have multiple active
>> subprojects.
> Anybody knowing a little about the world of replication needs will
> agre
stark <[EMAIL PROTECTED]> writes:
> There isn't really any need for the second pass in lazy vacuum if the table
> has no indexes.
How often does that case come up in the real world, for tables that are
large enough that you'd care about vacuum performance?
regards, tom lan
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> If we've got command stats turned on by default now, I'll have a hard
> time buying performance as any reason to turn the others off.
That's a mistaken argument, because the reason stats_command_string
is now on is that it was reimplemented in a way tha
Tom Lane wrote:
>
> My take on all this is that there's no one-size-fits-all replication
> solution, and therefore the right approach is to have multiple active
> subprojects.
Anybody knowing a little about the world of replication needs will
agree with you here. Unfortunately, AFAICS pgcluster c
On 8/27/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Well, make a list and tell the admins to delete those projects.
Alright. When I come across one, I'll forward it on.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33
Jonah H. Harris wrote:
> I'm not saying that *everything* on pgfoundry is junk... but I can
> start naming dead projects if you'd like.
Well, make a list and tell the admins to delete those projects.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
On 8/27/06, Gregory Stark <[EMAIL PROTECTED]> wrote:
I'm beginning to wonder whether it would be better from a PR perspective to
rename pgfoundry to something like modules.postgresql.org. While "modules"
isn't necessarily technically right in postgresql vocabulary it's right in the
more general s
David Fetter wrote:
> I think it's useful to mention what's arriving, what's being worked
> on, and what's not even being contemplated in the long term.
We don't even have a roadmap of any kind, so the last thing we can do is
put claims of that sort in the documentation.
> Similar troubles apply
Tom Lane <[EMAIL PROTECTED]> writes:
>> That said, my company would feel more confortable with the idea that it's
>> part of the postgresql mainstream distro for many obvious reasons - or we
>> might drop postgresql altogether - which is why I'm proposing myself to do
>> the necessary work to inte
25 matches
Mail list logo
