Re-sending since it did not reach the list the first time. My apologies if
the original ever does. (I had a DNS problem with my ISP).
--
Serguei A. Mokhov| /~\The ASCII
Computer Science Department | \ / Ribbon Campaign
Concordia University | XAgainst HTML
Montreal
You must have a broken version of make. There certainly is a 'clean'
rule in that subdirectory, and it works for everyone else.
regards, tom lane
Ah yes. Actually, this is the error I got once I manually created the
earthdistance directory in order for the clean to proceed. The fir
Hello Peter,
This patch completes translation of initdb for 7.5:
- Translate the remaining untranslated messages
- Proofread and run basic spellcheck
I plan no updates for this one until the string freeze.
Thanks,
-s
initdb-ru.po.gz
initdb-ru.po.gz
Description: GNU Zip compressed da
On Sat, 2004-05-29 at 15:02, Marc G. Fournier wrote:
> On Sat, 29 May 2004, Matthew T. O'Connor wrote:
> > I can wait, but I am really trying not to miss the feature freeze which
> > AFAIK, is still happening in a few days. Is that changing? Will I have
> > time if I wait a few days? Especially g
On Sat, 29 May 2004, Matthew T. O'Connor wrote:
On Sat, 2004-05-29 at 11:04, Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
It is supposed to be linked into the postmaster and forked from there.
In the current state of pg_autovacuum it wouldn't matter a lot, but
I am assuming that we
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Matthew T. O'Connor wrote:
>> I did understand Tom, but based on the hacker discussion I think the
>> "postmaster integration" will consist of the postmaster launching and
>> killing the pg_autovacuum standalone executable as required. In that
>> sens
On Sat, 2004-05-29 at 11:04, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > It is supposed to be linked into the postmaster and forked from there.
>
> In the current state of pg_autovacuum it wouldn't matter a lot, but
> I am assuming that we will soon migrate it to depend on b
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
> Sent: 29 May 2004 09:44
> To: Matthew T. O'Connor
> Cc: Tom Lane; pgsql-patches
> Subject: Re: [PATCHES] Moving pg_autovacuum from contrib to src/bin
>
>
> It is supposed to be linked into the postmaster and for
On Sat, 2004-05-29 at 02:15, Tom Lane wrote:
> "Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> > As outlined in my email, step 1 is to move pg_autovacuum from contrib to
> > src/bin. Attached is a patch that modifies src/bin/Makefile and the
> > pg_autovacuum Makefile which will be in src/bin/
Matthew T. O'Connor wrote:
> I did understand Tom, but based on the hacker discussion I think the
> "postmaster integration" will consist of the postmaster launching and
> killing the pg_autovacuum standalone executable as required. In that
> sense, I don't think it matters if pg_autovacuum is loc
Ok, based on feedback from Tom and Peter, here is another stab at moving
pg_autovacuum from: contrib/pg_autovacuum to: src/backend/postmaster
In summary pg_autovacuum.c has to be moved to src/backend/postmaster,
pg_autovacuum.h moves to src/include. The apply the attached patch
which makes the re
On Sat, 2004-05-29 at 02:45, Peter Eisentraut wrote:
> Matthew T. O'Connor wrote:
> > The only reason I put it in src/bin is because I thought people
> > wanted pg_autovacuum to still be a runable stand alone app.
>
> I see no reason for that. If it's integrated as a postmaster child,
> then it
12 matches
Mail list logo
