Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Sorry to hear that this is the way it turned out. It is a bad precedent
> imho, and I see no way forward on my interest in this area. Hopefully
> someone else will pick it up; perhaps one of those so vehemently against
> the details of this?
I said I
Yes, perhaps a bad precedent. I have very rarely done this. I do have
the patch here if anyone wants to use it. My guess is if someone
implements it, it will be done only in initdb, and use symlinks, which
you and Marc don't like, so we may be best leaving it undone for 7.3 and
returning with
> OK, with two people now asking to have the patch removed, and with no
> comment from Thomas, I have removed the patch. This removes XLogDir
> environment variable, and -X postmaster/postgres/initdb/pg_ctl flag.
> I have also removed the code that dynamically sized xlogdir.
... Back in town...
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, with two people now asking to have the patch removed, and with no
> > comment from Thomas, I have removed the patch. This removes XLogDir
> > environment variable, and -X postmaster/postgres/initdb/pg_ctl flag.
>
> I thought we
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, with two people now asking to have the patch removed, and with no
> comment from Thomas, I have removed the patch. This removes XLogDir
> environment variable, and -X postmaster/postgres/initdb/pg_ctl flag.
I thought we intended to keep the -X swit
OK, with two people now asking to have the patch removed, and with no
comment from Thomas, I have removed the patch. This removes XLogDir
environment variable, and -X postmaster/postgres/initdb/pg_ctl flag.
I have also removed the code that dynamically sized xlogdir.
I will post the patch to p
Curt Sampson wrote:
> On Thu, 15 Aug 2002, Bruce Momjian wrote:
>
> > I would like to know how to move this item forward.
>
> Right now (i.e., in 7.2), the only two options we have for moving the
> log file to a different spindle are mounting it on pg_xlog and using a
> symlink. I doubt many peo
On Thu, 15 Aug 2002, Bruce Momjian wrote:
> I would like to know how to move this item forward.
Right now (i.e., in 7.2), the only two options we have for moving the
log file to a different spindle are mounting it on pg_xlog and using a
symlink. I doubt many people do the the former, and if they
I would like to know how to move this item forward.
---
Tom Lane wrote:
> Curt Sampson <[EMAIL PROTECTED]> writes:
> > ... just for the record I'm with the "don't
> > use an environment variable" crowd here, too. It's way,
Curt Sampson <[EMAIL PROTECTED]> writes:
> ... just for the record I'm with the "don't
> use an environment variable" crowd here, too. It's way, way to easy
> to start up with the wrong setting in your environment.
What he said ...
> Oh, and yes, it does need to be changable after an initdb. Say
On Tue, 13 Aug 2002, scott.marlowe wrote:
> My non-coding vote goes with Tom Lane on this. initdb can set pg_xlog,
> and if you need to change it, use symlinks.
I've not been following this thread, and thus I suppose I missed
my opportunity to vote, but just for the record I'm with the "don't
u
On Tue, 13 Aug 2002, Bruce Momjian wrote:
> If you move pg_xlog, you have to create a symlink in /data that points
> to the new location. Initdb would do that automatically, but if you
> move it after initdb, you would have to create the symlink yourself.
> With Thomas's current code, you would
On Mon, 12 Aug 2002, Thomas Lockhart wrote:
> > If you move pg_xlog, you have to create a symlink in /data that points
> > to the new location. Initdb would do that automatically, but if you
> > move it after initdb, you would have to create the symlink yourself.
> > With Thomas's current code,
Yea, the problem with postgresql.conf is that we don't have any
automatic modifications of that file, and I don't think we want to start
just to avoid symlinks.
I personally like symlinks too. I use them all the time. What is the
problem with them, exactly? Can someone show me some commands t
Oliver Elphick <[EMAIL PROTECTED]> writes:
> On Tue, 2002-08-13 at 14:24, Tom Lane wrote:
>> But there's more than one way to record the xlog location in the data
>> directory. If you don't like a symlink, what of putting it in
>> postgresql.conf as a postmaster-start-time-only config option?
>
Rod Taylor <[EMAIL PROTECTED]> writes:
> Symlinks seem to break all over the place (windows, novell, os/2),
The portability argument carries little weight with me. Recent versions
of Windows have symlinks. If anyone wants to run a PG installation on
a symlink-less platform, okay; they just won'
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> One thought at the back of my mind is why not have something like a
> 'PG_VERSION' for XLOG? Maybe something so simple as a text file in both
> the data and xlog directory that just contains a timestamp from the
> initdb? then, when you startup p
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> In the spirit of gratutious overstatement, I'll point out again:
> symlinks are evil.
Please justify that claim. They work really nicely in my experience...
and I don't know of any modern Unix system that doesn't rely on them
*heavily*.
Possibly mor
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> We will? It looks to me like Thomas lost the vote 2-to-1.
> Well, you didn't vote again in my follow up email,
I thought my vote was obvious already ...
> Can two guys override another guy if he is doing the work? I usually
> like
> > OK, seeing as no one voted, and only Tom and I objected originally, we
> > will keep the code as Thomas has applied it, namely that PGXLOG/-X is
> > recognized by initdb, postmaster, postgres, and pg_ctl.
>
> We will? It looks to me like Thomas lost the vote 2-to-1.
>
> Unless there are mo
> If you move pg_xlog, you have to create a symlink in /data that points
> to the new location. Initdb would do that automatically, but if you
> move it after initdb, you would have to create the symlink yourself.
> With Thomas's current code, you would add/change PGXLOG instead to point
> to the
Marc G. Fournier wrote:
> > Well, you didn't vote again in my follow up email, so I thought you
> > didn't care anymore, and Thomas didn't reply to my email either. I am
> > clearly concerned, as you are, but Thomas isn't, and no one else seems
> > to care.
>
> k, why are you concerned? see my
Marc G. Fournier wrote:
> On Tue, 13 Aug 2002, Tom Lane wrote:
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, seeing as no one voted, and only Tom and I objected originally, we
> > > will keep the code as Thomas has applied it, namely that PGXLOG/-X is
> > > recognized by initdb, postm
On Tue, 13 Aug 2002, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, seeing as no one voted, and only Tom and I objected originally, we
> > > will keep the code as Thomas has applied it, namely that PGXLOG/-X is
> > > recognized by initdb, postmaster
On Tue, 13 Aug 2002, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, seeing as no one voted, and only Tom and I objected originally, we
> > will keep the code as Thomas has applied it, namely that PGXLOG/-X is
> > recognized by initdb, postmaster, postgres, and pg_ctl.
>
> We
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, seeing as no one voted, and only Tom and I objected originally, we
> > will keep the code as Thomas has applied it, namely that PGXLOG/-X is
> > recognized by initdb, postmaster, postgres, and pg_ctl.
>
> We will? It looks to me
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, seeing as no one voted, and only Tom and I objected originally, we
> will keep the code as Thomas has applied it, namely that PGXLOG/-X is
> recognized by initdb, postmaster, postgres, and pg_ctl.
We will? It looks to me like Thomas lost the vote 2
OK, seeing as no one voted, and only Tom and I objected originally, we
will keep the code as Thomas has applied it, namely that PGXLOG/-X is
recognized by initdb, postmaster, postgres, and pg_ctl. There is no
symlink from the /data directory to the WAL location.
Thomas, you mentioned implement
On Fri, Aug 09, 2002 at 06:54:44PM -0700, Thomas Lockhart wrote:
> I had thought to extend the capabilities to allow resource allocation
> for individual tables and indices, which has *long* been identified as a
> desired capability by folks who are managing large systems.
Without wishing to po
Thomas Lockhart wrote:
> > Thomas, would you remind me of the concusions because I thought everyone
> > involved felt that it should be an initdb-only option, but I still see
> > it in CVS.
>
> ?? "Concussions" as in brain bruises? ;)
Uh, conclusions. Sorry. New keyboard desk in new house. :-)
> Thomas, would you remind me of the concusions because I thought everyone
> involved felt that it should be an initdb-only option, but I still see
> it in CVS.
?? "Concussions" as in brain bruises? ;)
I'm not sure I understand the question. I assume that we are talking
about the WAL log locatio
Thomas, would you remind me of the concusions because I thought everyone
involved felt that it should be an initdb-only option, but I still see
it in CVS.
---
Thomas Lockhart wrote:
> > Thomas, have you commented on the obj
32 matches
Mail list logo
