a/SCO OpenUnix box using Linux emulation thanks to
Larry Rosenman, even though I've not availed myself of that access as yet.
Other none-RedHat RPM-based distributions are not directly supported by me,
although SuSE 7.3 on UltraSparc may be supported in the future, as I have an
Ultra 5 ru
[Trimmed CC list]
On Sunday 14 April 2002 01:52 am, Hannu Krosing wrote:
> On Sun, 2002-04-14 at 08:48, Lamar Owen wrote:
> > Incidentally, the 7.2.93 (skipjack) public beta is a serious improvement
> > over RHL 7.2, and I personally recommend it, as KDE 3 is worth the
> > up
On Sunday 14 April 2002 03:00 pm, Luciano Miguel Ferreira Rocha wrote:
> On Sun, Apr 14, 2002 at 02:35:13PM -0400, Lamar Owen wrote:
> > Raw performance seems to be increased as well, due to an improved kernel
> > (2.4.18 plus low-latency and preemptible patches, accordin
re rolled back in aborted transaction
This seems the correct behavior.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
for Mandrake!
That's good news. Really good news.
The delay was worth it, I guess. I have also had a report of a Red Hat 7.1
user getting a rebuild without difficulty. Good things.
Although I wonder how many have downloaded the Red Hat 6.2 SPARC RPM's I
uploaded. :-)
--
Lamar Ow
, and PostgreSQL would exist
afterwards -- that is, after all, the beauty of free software.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomai
u just built.
There was another fellow built the RPMset on RH 7.1 a week or so ago, and he
said the rebuild worked just fine.
As I don't have a RH 7.1 machine to build on, this is the best I can do.
Sorry.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end o
#x27;re all
here. s/Free/Open Source/g if you'd rather not invoke a stallmanism. Or
even s/Free/BSD-licensed/g if you want to really state the obvious. :-)
If other projects' members are insulted by that, then they're just too
sensitive.
--
Lamar Owen
WGCR Internet Radio
1 Peter
some baroque dependencies, I still have a client
running RedHat 5.2 in production. Not pretty to support. Still at 6.5.3,
too.
We need a better upgrade path, but that's a different discussion.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)
stgresql.org/cvsweb.cgi/pgsql/)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Thursday 09 May 2002 07:51 am, Marc G. Fournier wrote:
> On Wed, 8 May 2002, Lamar Owen wrote:
> > > 3) If (2) is the case, then development could continue under the BSD
> > > license, since developers could use the BSD-original code for their
> > > developmen
32 _is_ an inferior
server platform, at least in my opinion. But, if you want to do the work,
and it doesn't break my non-Win32 server build, by all means go for it.
With that said, I hope you'll consider sticking it out and seeing it through
at least two major cycles.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
bug.
Tom (or Thomas):
Where would we go to ferret out the source of this bug? More to the point: we
need a test case in C that could expose this as a glibc bug. Methinks Red
Hat would want this bug ferretted out, as it would likely cause problems with
RedHat Database on RH 7.3's glibc.
[HACKERS added to cc:, GENERAL dropped]
On Monday 20 May 2002 11:39 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Well, I went to bat for this a little bit ago, relating to a bug report,
> > but I've struck out. The ISO C standard spells it out pla
ml#tag_04_14
for the definition of 'Seconds Since the Epoch', then cross-reference to the
man page of mktime.
I don't like it any more than you do, but that is the letter of the standard.
Thomas, any comments?
Our implementation is broken, then. Thomas, is this fixable for a 7.
;s mktime (which I have
on hand), but I guess I will take a look now);
2.) Rewrite our stuff to not depend on any mktime, and thus be more portable
(perhaps?).
But, in any case, I didn't mean to step on your toes by any of my comments; I
completely agree with you that glibc and the
Complain to Red Hat. Loudly. However, as this is a glibc change, other
distributors are very likely to fold in this change sooner rather than later.
Try using timestamp without timezone?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end
On Tuesday 21 May 2002 12:31 pm, Trond Eivind Glomsrød wrote:
> On Tue, 21 May 2002, Lamar Owen wrote:
> > However, as this is a glibc change, other
> > distributors are very likely to fold in this change sooner rather than
> > later.
> Relying on nonstandardized/nond
an easy one.
We have gotten blind to the regular locale-induced failures -- this is not a
good thing.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Tuesday 21 May 2002 06:09 pm, Oliver Elphick wrote:
> On Tue, 2002-05-21 at 18:24, Lamar Owen wrote:
> > In any case, this isn't just a Red Hat problem, as it's going to cause
> > problems with the use of timestamps on ANY glibc 2.2.5 dist. That's more
>
guys.
> :-) Very funny.
What isn't funny is Oliver Elphick's results on Debian, running glibc 2.2.5
(same as Red Hat 7.3's version). They are different. And, IMO, those
results are the 'expected' results on a unixoid system, ISO or no ISO.
--
Lamar Owen
WGCR Inter
On Wednesday 22 May 2002 01:58 pm, Ulrich Drepper wrote:
> On Wed, 2002-05-22 at 10:51, Lamar Owen wrote:
> > What isn't funny is Oliver Elphick's results on Debian, running glibc
> > 2.2.5 (same as Red Hat 7.3's version).
> This is a completely different versio
t willing to patch away) get this
braindead behavior. Oh well. The general solution will happen.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
ode.
However, I do think at that point we need to look at what the patch manager
(historically Bruce) can deal with realistically. Is it a job for two patch
managers, one for the STABLE and one for the DEV? Only Bruce can answer
whether he can realistically handle it (I personally h
On Monday 10 June 2002 04:11 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Historically we've concentrated our development efforts during beta to
> > 'fixing beta problems only'
> There is a downside to changing away from that approach.
On Thursday 20 June 2002 02:57 pm, Jan Wieck wrote:
> set of triggers where working, and then Stephan did all the others and I
> forgot who else helped to do the utility commands and CREATE TABLE
> syntax and tried to decrypt the SQL definitions?
Don Baccus?
--
Lamar Owen
WGCR Interne
e
> Postgres community.
I like this idea, but let me just bring one little issue to note: are you
going to handle upgrades, and if so, how? How are you going to do a major
version upgrade?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)--
27;in place' upgrading. He has been able to
write code to read multiple versions' database structures -- proving that it
CAN be done.
Windows programs such as Lotus Organizer, Microsoft Access, Lotus Approach,
and others, allow you to convert the old to the new as part of initial
On Tuesday 02 July 2002 03:14 pm, Jan Wieck wrote:
> Lamar Owen wrote:
> > [...]
> > Martin O has come up with a 'pg_fsck' utility that, IMHO, holds a great
> > deal of promise for seamless binary 'in place' upgrading. He has been
> > able to
ieve a backend-independent data dumper would be very useful in many
contexts, particularly those where a backend cannot be run for whatever
reason, but you need your data (corrupted system catalogs, high system load,
whatever). Upgrading is just one of those contexts.
--
Lamar Owen
WGCR
On Saturday 06 July 2002 11:15 am, Tom Lane wrote:
> Andrew Sullivan <[EMAIL PROTECTED]> writes:
> > On Fri, Jul 05, 2002 at 12:39:13PM -0400, Lamar Owen wrote:
> >> One other usability note: why can't postmaster perform the steps of
> >> an initdb if -D p
upgrading. And I'm talking about dumping
the binary down to ASCII to be restored, not binary to binary on the fly.
This is the best dialog yet on the issue of upgrading. Keep it coming! :-)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)--
that
requires any portion of an old package to remain around. The new package
must be self-contained and must be able to upgrade the old data, or they will
not accept it.
Their statement now is simply that PostgreSQL upgrading is broken; dump before
upgrading and complain to the PostgreSQL de
course be
> 1) run pre-upgrade (pg_dumpall >dumpfile)
> 2) upgrade
> 3) run post-upgrade (initdb; psql < dumpfile)
All but the first step works fine. The first step is impossible in the
environment in which the %pre script runs.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
On Tuesday 09 July 2002 04:17 pm, Hannu Krosing wrote:
> On Tue, 2002-07-09 at 22:10, Lamar Owen wrote:
> > The pre-upgrade script is run in an environment that isn't robust enough
> > to handle that. What if you run out of disk space during the dump?
> You can either ch
e at all coherent -- but my stream of
consciousness rarely is [coherent]). Can our core be written/rewritten in
such a way as to be _completely_ object driven? Someone steeped a little
better in object theory please take over now....
Or am I totally out in left field h
On Tuesday 09 July 2002 07:19 pm, Rod Taylor wrote:
> On Tue, 2002-07-09 at 19:09, Lamar Owen wrote:
> > And what if you have enough disk space to do the dump, but then that
> > causes the OS upgrade to abort because there wasn't enough space left to
> > finish upgrading
[replying to myself]
On Tuesday 09 July 2002 07:34 pm, Lamar Owen wrote:
> if you do this. Already RPM can rollback the transaction being done on the
> RPM database (it's a db3 database system), but rolling back the filesystem
> is a little different.
As a note of interest, RPM it
e for documentation purposes only ... Greetings from the MySQL
> documentation ;-)
Is sarcasm really necessary?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropri
[cc: trimmed]
On Wednesday 10 July 2002 03:42 am, Jan Wieck wrote:
> Lamar Owen wrote:
> > As a note of interest, RPM itself is backed by a database, db3. Prior to
> > version 4.x, it was backed by db1. Upgrading between the versions of RPM
> > is simply -- installin
On Wednesday 10 July 2002 09:11 am, Hannu Krosing wrote:
> On Wed, 2002-07-10 at 01:09, Lamar Owen wrote:
> > The wc utility isn't in the path in an OS install situation. The df
> > utility isn't in the path, either. You can use python, though. :-) Not
> > tha
On Wednesday 10 July 2002 11:48 am, Hannu Krosing wrote:
> On Wed, 2002-07-10 at 16:20, Lamar Owen wrote:
> > On Wednesday 10 July 2002 09:11 am, Hannu Krosing wrote:
> > > And I have written custom postgres table dumpers in python without too
> > > much effort (exc
stuff, particularly the fortran to python
translator.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so tha
On Wednesday 10 July 2002 04:42 pm, Jan Wieck wrote:
> Lamar Owen wrote:
> > On Wednesday 10 July 2002 03:24 am, Jan Wieck wrote:
> > > The problem why this conflicts with these package managers is,
> > > because they work package per package, instead of looking at the
nyway converting to slope-intercept, if indeed that is the internal
representation. So why not dump in slope-intercept form, if that is the
internal representation?
But, you're telling me floats aren't dumpable/restoreable to exactly the same
value? () This can't be g
> They are different. One is infinite in length, the other is finite.
> Distances, etc are calculated differently between the two types.
For some of my work a type of 'ray' would be nice... :-) But LSEG's usually
work OK as long as you specify an endpoint that is far enough away
it config patch'. Also see 'Thoughts on the location of
configuration files' and 'Explicit configuration file'.
Explaining what you mean by the potential security implications would be nice.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ne, we increase substantially the odds of
> >> creating an exploitable security hole.
> > Ok, true enough, but I'm not sure that a config file or any other
> > such mechanism is any safer. As Lamar Owen said, anyone who can
> > poison the postgres user's enviro
On Tuesday 30 July 2002 07:46 pm, Curt Sampson wrote:
> On Tue, 30 Jul 2002, Lamar Owen wrote:
> > I said it. In any case, using strings that are in the environment
> > requires an untrusted PL, or a C function.
> Ah. See, we already have a failure in a security analysis he
On Tuesday 30 July 2002 11:51 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> >> CREATE DATABASE foo WITH LOCATION = 'BAR'
> > And requires you to be a database superuser anyway.
> CREATE DATABASE does not require superuser privs, only creat
was not reached as I recall.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
like it. It
is a good client, don't get me wrong: but DBD:Pg is the standard now.
But, if you are an RPM user, you can already just download the pieces for a
minimal client-side system. And you have been able to do so for right at
three years, give or take.
--
La
g == DBI right ? not pg.pm
Right.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
his patch as I can and see what will be required
to make this work in CURRENT.
IMO, the key is that if the switch is not specified the current behavior is
default. If specified, it will do its thing.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Thursday 01 August 2002 02:21 pm, Bruce Momjian wrote:
> Bruce Momjian wrote:
> > Lamar Owen wrote:
> > > And the sooner our very old perl client goes away, the better I like
> > > it. It is a good client, don't get me wrong: but DBD:Pg is the
> > >
ng the tree; and that was a good
feeling.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
mess
onfig files.
You had an idea along these lines, and I was quite OK with the majority of it.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Thursday 01 August 2002 05:22 pm, Bruce Momjian wrote:
> Lamar Owen wrote:
> > It's already in CPAN. A link to CPAN should suffice, IMHO.
> > I also thought we were discussing trimming the tree; and that was a good
> > feeling.
> Lamar, you said earlier today
if I have this all
> > wrong...)
You have this wrong. The distributions do periodically sync up with my
revision, and I with theirs, but they do their own packaging.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ave the largefile support available, so on those distributions the
support will have to be unavailable -- and the decision to build it or not to
build it must be automatable.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
h hard drives available).
The source RPM will still be useful to the newer distribution's maintainers
-- but the requests I see more of on the lists is newer PostgreSQL on older
linux. So I'm going to try to rise to that occassion, and take this
opportunity to apologize for n
On Monday 12 August 2002 09:51 pm, Karl DeBisschop wrote:
> On Mon, 2002-08-12 at 21:28, Lamar Owen wrote:
> > I'm going to now go to the lagging plane -- building newer PostgreSQL for
> > older Red Hat (and maybe others, if I can get enough hard drives
> > available).
u see zero value in
Knowing Don to some extent, I can say with some assurance that his 'attacks'
are never unprovoked.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Tuesday 13 August 2002 08:07 pm, Curt Sampson wrote:
> On Tue, 13 Aug 2002, Lamar Owen wrote:
> > > Curt, I think his reply stems from his frustration of chosen content in
> > > many emails that originate from you. We all pretty well understand
> > > postgres
gt; This could be done in the regression test driver, where the correct path
> is available as $pkglibdir. Other, less messy solutions don't occur to me
> offhand.
The RPM's patch the regression tests to work -- in a somewhat broken way, but
enough to get useful results. IIRC, I
otation is more of a 'divider' than the @. Unless there is some _really_
good reason to not use !, that is. :-)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
he solution
is that wherever a user name is to be stored, the fully qualified form must
be used and checked against, with @template1 being a 'this user is
everywhere' shorthand.
But maybe I'm just misunderstanding the implementation.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4
On Wednesday 14 August 2002 03:55 pm, Vince Vielhaber wrote:
> On Wed, 14 Aug 2002, Lamar Owen wrote:
> > If the user 'lowen' is then expanded to 'lowen@template1' it would be
> > stored that way -- and lowen@template1 is different from lowen@pari, for
> >
nadorned usernames, and giving inherited rights
across the installation to users with template1 rights? Then you have the
unadorned 'lowen' becomes 'lowen@template1' -- but lowen@pari wouldn't have
access to template1, right? Or am I misunderstanding the featu
On Wednesday 14 August 2002 03:04 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Appending '@template1' to unadorned usernames, and giving inherited
> > rights across the installation to users with template1 rights? Then you
> > have
On Wednesday 14 August 2002 03:49 pm, Bruce Momjian wrote:
> Lamar Owen wrote:
> > On Wednesday 14 August 2002 03:29 pm, Vince Vielhaber wrote:
> > > Hate to complicate things more, but back to a global username, say
> > > you have user "lowen" that shoul
I know I sound like a broken record (for those who remember vinyl records),
but good upgrading tools would eliminate this recurring problem. That's all
I'm saying about that this time -- I've said enough, and it's all archived
for those who care to know what I think about t
am of course OK with it.
:-) Easier to type than user@template1, too.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
s pg_dump for
things). If the upgrade was painless, I'd agree that 7.3 is the solution --
but a real security fix shouldn't wait for 7.3. But I'm holding judgment on
a proven exploit. A proven exploit will change my mind to say 'we need a
7.2.2 NOW that fixes
On Tuesday 20 August 2002 12:15 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Umm, but what about the reply buffer overrun advisory? I've read this
> > whole thread, and the reply advisory (AFAICT, unless I've just hit delete
> > too quick
, make somewhat of a 'splash'
when diving in. :-)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
essibility is OFF by
default.
I for one thought that it was normal operating procedure to only allow access
to trusted machines; maybe I'm odd in that regard.
Hey, if I can connect to postmaster I can DoS it quite easily, but flooding it
with connection requests.
But, if we can thwart this,
nickname -- Hmmm, 'SMitTy' perhaps? :-) Reminds me of
'Uncle George' who did quite a bit for the Alpha port and then disappeared.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ary/v7.2.2/RPMS/redhat-7.3
Source RPMS at
ftp://ftp.postgresql.org/pub/binary/v7.2.2/RPMS/SRPMS
No SPARC binaries for Red Hat 6.2 yet... :-)
CHANGELOG:
* Mon Aug 26 2002 Lamar Owen <[EMAIL PROTECTED]>
- 7.2.2-1PGDG
- Applied PeterE's contrib patch -- contrib is now completely restru
ph One is Elias Levy, then that's easy
enough. If the information is easily available, then that's enough.
So, it makes a difference to me, like it, lump it, or think it's insane.
And, yes, I agree he IS providing a valuable service -- with that I have no
complaints. But
ead, that's all. The substance is OK; the presentation is lacking,
IMHO.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ment than I was that this is the right answer to this issue.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
On Tuesday 27 August 2002 03:43 pm, Bruce Momjian wrote:
> Lamar Owen wrote:
> > On Tuesday 27 August 2002 03:19 pm, Bruce Momjian wrote:
> > I thought it WAS resolved, to do:
> > > Tom likes this because it is the fewer global users who have to append
> > > t
On Wednesday 28 August 2002 10:35 am, Marc G. Fournier wrote:
> having never had to do it before, do you know what the procedure is?
Post to [EMAIL PROTECTED] -- it's moderated, and I don't know if
there's a subscription requirement.
--
Lamar Owen
WGCR Internet
On Wednesday 28 August 2002 02:32 pm, Lamar Owen wrote:
> On Wednesday 28 August 2002 10:35 am, Marc G. Fournier wrote:
> > having never had to do it before, do you know what the procedure is?
>
> Post to [EMAIL PROTECTED] -- it's moderated, and I don't know if
sufficiently widely
> depended on that I think it ought to follow the same quality standard
> as the main backend ... viz, "no new features during beta".
Does this mean we should be looking for a way to integrate it into the main
backend at this point? Isn't that what contr
On Friday 30 August 2002 09:29 am, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Does this mean we should be looking for a way to integrate [FTI] into the
> > main backend at this point? Isn't that what contrib is for?
> Well, given that Chris a
s
in their own build systems.
If someone can figure out how to override the default, then they can deal with
the results, IMHO.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
at need
massaging, if it can be done that easily.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
w big is the problem? It's looking bigger with each passing day, ISTM.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
On Wednesday 11 September 2002 09:44 pm, Bruce Momjian wrote:
> Lamar Owen wrote:
> > Bruce, I mentioned a sed/perl/awk script already to massage the dump into
> > a 7.3-friendly form -- but we need to gather the cases that are involved.
> > Methinks every single OpenACS
I haven't had time to
go through it with the properly fine-toothed comb that I want to as yet. I
would expect to be able to release an RPMset for beta 2 if that is a week or
two off.
I'll try to keep everyone who cares updated periodically.
--
Lamar Owen
WGCR In
; the ISOC application for management of the .org namespace.
Talk about full circle. See my e-mail address's domain to get the punch line.
In more than one way WGCR relies on PostgreSQL for mission-critical data
storage.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-
On Tuesday 17 September 2002 03:59 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > as yet. I would expect to be able to release an RPMset for beta 2 if
> > that is a week or two off.
> Given that we'll be forcing an initdb for beta2 anyway, those
On Tuesday 17 September 2002 04:40 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > ... What I am looking
> > at is whether the user will have to run 7.3's pg_dump in order to migrate
> > older data.
> AFAIK this is not *necessary*, though it
On Tuesday 17 September 2002 10:27 pm, Christopher Kings-Lynne wrote:
> Lamar Owen wrote:
> > Sorry, it's just a sore spot for me, this whole
> > upgrade issue.
> IS there any solution to Postgres's upgrade problems? I mean, ever? With
> the complex catalo
gration went
smoothly -- but there were less than ten thousand records at that point.
So I _do_ have a three-year old database sitting there. Rock solid except for
one or two times of wierd vacuum/pg_dump interactions, solved by making them
sequential.
--
Lamar Owen
WGCR
On Tuesday 17 September 2002 11:51 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> >> How does pg_upgrade work?
> > [ pretty good description ]
> You missed a key point, which is that pg_upgrade does not even try to
> cope with version-to-versi
On Wednesday 18 September 2002 12:55 am, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Not talking about a freeze. Talking about separation of system/feature
> > metadata from user metadata that wouldn't change in the upgrade anyway --
> But the
http://developer.novell.com/connections/091902.html
I'm somehwat surprized no one else has mentioned this, as it's on Slashdot...
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our ext
1 - 100 of 513 matches
Mail list logo
