re BETA
QUALITY RPMS -- BY REQUEST. Please don't make me regret not waiting until a
release candidate :-).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Peter Eisentraut wrote:
> Lamar Owen writes:
> > Ok, I have a first set of 7.1beta3 RPMs uploading now. These RPMs pass
> > regression on my home RedHat 6.2 machine, which has all locale environment
> > variables disabled (/etc/sysconfig/i18n deleted and a reboot).
> So
exists in one of the
system catalogs now -- it just has to be made accessible.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Trond Eivind Glomsrød wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> > > Re: rpm-pgsql-7.1beta3.patch
> > > | diff -uNr postgresql-7.1beta3.orig/src/Makefile.shlib
>postgresql-7.1beta3/src/Makefile.shlib
> > > | - L
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > doing. This is a fix for the broken rpm setup found on Linux-PPC, as
> > found by Tom Lane. It would be marvelous if this would be expendable at
> > this juncture.
> It is. 7.1 builds cleanly on PPC
Tom Lane wrote:
> Let me know when you think the 7.1 RPM specfile is stable enough to be
> worth testing, and I'll try to build PPC RPMs.
Ok. Should be coincident with -2. I'm planning to have a -2 out later
this week.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
n (or their symlinks) will always live.
> I was thinking in terms of fixing this in the source tree.
Oh.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
w you have good
reasons -- I'd like to see them as well, for the same reasons as I'd
like to see Trond's.
We're early in the RPM beta cycle here -- many things can and will
change before final.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Trond Eivind Glomsrød wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > In particular, this was and is a RedHat-made change. It does not break
> > anything that I am aware of, and allows the distributions to do their
> > thing as well.
> Note that this wasn
from prior RPM's removed from spec file.
pg_config in -devel rpm.
pg_upgrade removed.
And others -- see the changelog in the spec file.
BETA TEST USE ONLY!
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
n 100MB per day out of my http (backed by PostgreSQL since late
1997!), but the 2.5GB a day out the RealServer is the big hit
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Tom, try out a PPC build on this one. I know of one problem that I have
> > to fix -- postgresql-perl fails dependencies for libpq.so (I backed out
> > the patch to Makefile.shlib).
> The backend se
l 0' --rebuild .
Thanks to Tom Lane for finding this.
Sorry for the inconvenience.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
is not the easiest in the world
-- please be sure to read the README.rpm-dist file in the main
postgresql RPM.
Also, you will need to read this file to see which packages you want --
for a full client-server install, install postgresql and
postgresql-server. Pick and choose the other clients
cial RPMs, including financial assistance (:-)), servers
running the distributions in question for building/testing, and top-tier
professional feedback (when they say this release has been
professionally QA tested, they _mean_ it!) on my little project.
Kudos to GreatBridge!
--
Lamar Owen
WGCR
ll work on others. The hooks are there now for SuSE -- just some
fill-in work left to be done.
Portability is hard. C programmers have known this for some time -- but
the RPM specfile doesn't really lend itself to vast portability.
Although, I am learning some real tricks that really help.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
), is several months at the very least
down the road makes it desireable NOW to have the LAZY behavior.
I for one don't _need_ the LAZY behavior -- my VACUUMs take seconds, not
hours.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
of others, of course.
But, Peter's point does hold -- someone will have to maintain this.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
the instance of pg_dumplo -- can I get some ideas on it? Should
it be shipped as a separate package, or in the -server subpackage, or??
I am open to suggestions.
If PORTS is a more appropriate list to post this, I will do that as
well.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
> >and the distiction between core and contrib programs will not be fuzzy.
>
> This is what I do for the Debian release.
Precedent set; precedent followed. I'll be hopefully packaging the
_entire_ contrib tree :-) for beta 4, over the weekend.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Tom Lane wrote:
> Meanwhile, it's not the RPMs' place to editorialize on which contrib
> items are useful. Package 'em all, unless we hit build problems.
Interesting point of view :-). Going into 'Uncle Martin' mode (obscure
joke alert...).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
or such a file.
Comments? _Why_ is the lock in /tmp? Won't the lock always be put into
place by the uid used to run postmaster? Is a _world_ writeable
temporary directory the right place?
7.2 discussion, however, IMHO.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
The Hermit Hacker wrote:
> On Sat, 27 Jan 2001, Lamar Owen wrote:
> > Comments? _Why_ is the lock in /tmp? Won't the lock always be put into
> > place by the uid used to run postmaster? Is a _world_ writeable
> > temporary directory the right place?
> first off,
Peter Eisentraut wrote:
> Lamar Owen writes:
> > I understand why the socket needs to be in /tmp, but why the lockfile?
> The lock file protects the Unix domain socket. Consequently, the name of
> the lock file needs to be derivable from the name of the socket file, and
>
prefer to leave closer to what 7.0
had).
The change in question is the use of '/usr/share/postgresql' and
'/usr/include/postgresql' as part of the installation, rather than
allowing '/usr/share/pgsql' and '/usr/include/pgsql' .
O well -- I'm just going to have to see how it distills. I've not
received any complaints yet, but I expect many after final. :-(
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Trond Eivind Glomsrød wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Trond Eivind Glomsrød wrote:
> > > Not to sound scheptical, but since when did postgresql care about
> > > backwards compatiblity? Upgrading is already demanding a lot of
> > U
Peter Eisentraut wrote:
> Lamar Owen writes:
> > But, let me ask this: is it a good thing for PostgreSQL clients to have
> > hard-coded socket locations? (Good thing or not, it exists already, and
> > I know it does)
> Perhaps there could be some sort of /etc/post
iscussion, a compromise will have to be arranged -- but
this really isn't a 7.1 issue, as this isn't a 'bugfix' per se -- you
have fixed the immediate problem. But this is something to consider for
7.2 or later, as priorities are shuffled.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > How about an environment variable? PGSOCKLOC? Use the hard-coded
> > default if the envvar not set? This way multiple postmasters running on
> > multiple sockets can be smoothly supported.
> It's s
Looks like the same thing is going to happen with RedHat's
distribution. So, if this is going to occur, let's get a consensus as
to where that alternate location (barring some other solution) is going
to be, so that there are the fewest variants out there.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Lamar Owen wrote:
> Tom Lane wrote:
> > It's spelled PGHOST as of 7.1 ... but the discussion here is about what
> > the default behavior of an installation will be, not what you can
> > override it to do.
> I'm talking about Unix domain socket location, not
er can easily find it with
pg_config, if a static linkage or binary-only custom client that
directly accesses the fe-be protocol (are there any that we know
about?).
But we don't need to spend a great deal of time on it, regardless.
Speaking of time to spend, are we a 'go' for bet
hanges to any locks
or sockets, either :-).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
'll kindly not exaggerate the importance -- but I would have seen
reports had the simple fix not been applied.
But I'm not going to spend any more time arguing about it, that much is
certain. I've got other fish to fry, like beta4 RPM's.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Bruce Momjian wrote:
> Lamar Owen wrote:
> > Bruce Momjian wrote:
> > > No one has suggested a location non-root people can put the socket/lock
> > Since RPM's _must_ be installed by root, that doesn't affect them. The
> The issue we have is that we
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > But my issue is that libpq or any other client should be smart enough to
> > not have to assume the location.
> Er, how do you propose to do that? The client cannot learn the correct
> location from the po
l_schedule
RPMs passed regression (except for locale errors) on my RedHat 6.2 devel
machine.
I have changed the absolute minimum from beta3-2. Please let me know
any problems you find!
I am for now leaving the 7.1beta3-2 RPMset up.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > How does netstat find out?
> netstat burrows around in kernel datastructures, is how.
> I don't see invoking netstat as a solution anyway. For one thing,
> it's drastically nonstandard; even if ava
Lamar Owen wrote:
> ftp://ftp.postgresql.org/pub/dev/test-rpms is the place.
One note: for whatever reason the date on the uploaded RPM's has the
wrong year -- but the timestamp on my local copy has the correct date.
In any case, ignore the datestamp on those RPM's -- there wer
x27;s just the first line, as most
Received: headers are multiline. After adding up all the other X-
headers, I'm sure we could trim that down further.
It can also be compressed, if we want.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Bruce Momjian wrote:
>Lamar Owen wrote:
> > Yow! Nice stuff in there, that is for sure. Of course, that's alot of
> > space. What to do? Remove all the unnecessary e-mail headers?
> I just tried 'printmail' that strips off most of the unused stuff:
[...]
&g
just switch over to syslog as the standard log
> > destination...
> Not as long as all the good stuff goes to stderr.
> I think the -w thing and the log output thing should be fixed before 7.1
> goes out the door. Any comments on the particulars?
Where can elog() not be safely used? I'll volunteer to grep and
replace, subbing appropriate elog parameters, but I'm not sure I can do
it in time for 7.1's release.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
. (1MB of _headers_? Yow!)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
option for
> your gcc?
No. Full tree takes at minimum 36MB -- even pulling the _entire_
src/include tree over is only 2MB.
> I expect header files on /usr/include/pgsql for client programming not
> for SPI.
Why? I know of several people doing SPI work with no source tree
installed.
-
'm just being a little more specific). The contents of
-devel-spi (or maybe just -spi) would be all the other headers (no
duplicates) (again, expounding upon what Tom said already).
Comments?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
d be, but if
> people like this idea I will do the legwork to make the list.
Count me as liking it.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
changes there.
Sounds good to me. It appears that you haven't checked in your changes
to CVS as of a few minutes ago, but I like the looks of what you've
posted.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
he logs. We're not
> > replacing the system fprintf , are we? (my assumption is that we are
> > NOT). The usage of puts(), OTOH, has been well nigh eradicated.
Where is elog() safe? (Going to Bruce 'comb through the archives' mode
here...)
If someone can educate me i
lready have generic
log analysis tools set up to work with the OS vendor's logrotate, etc,
it pays to not reinvent the wheel but use the conventions and tools
already provided in the OS. Syslog is a standard way to do this.
Why even have syslog support otherwise? (Extremist? Maybe.)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
"Dominic J. Eidson" wrote:
> On Thu, 8 Feb 2001, Lamar Owen wrote:
> > A syslogger of stderr would make a nice place to pipe the output :-).
> > 'postmaster 2>&1 | output-to-syslog-program -f facility.desired' or
> 2>&1 | logger -p
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > AOLserver is one example that successfully redirects dynamic linker
> > messages to it's own log.
> Oh? How? Are you sure they're not just piping stderr to a program
> of their own devising? T
tion that works is better than mucking around with
the core, particularly this close to release.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
While I want to make sure that a
broken locale data set isn't used, I also want to make sure that a good
locale set isn't thrown out, either. Forcing to LC_COLLATE=C is
overkill, IMHO. And building without locale support doesn't work,
either, because, at least on RH 6.1, strncmp
Peter Eisentraut wrote:
> Lamar Owen writes:
> > And building without locale support doesn't work, either, because, at
> > least on RH 6.1, strncmp() is buggered to use the locale's collation.
> I don't think so. On RH 6.1, strncmp() is the same it's eve
t in a non-locale
RPM distribution, or? The locale enabled regression results fail due to
currency format and collation errors. Diffs attached. I'm not sure I
understand the select_views failure, either. Locale used was en_US.
Comments?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
locale-run.diffs
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > The locale enabled regression results fail due to
> > currency format and collation errors. Diffs attached. I'm not sure I
> > understand the select_views failure, either. Locale used was en_US.
>
Bruce Momjian wrote:
> In fact, the kernel doesn't even contain have a way
> to measure microsecond timings.
Linux has patches available to do microsecond timings, but they're
nonportable, of course.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
. RPM is pretty good at cleaning the old out.
Sometimes a little too good :-/.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
.2.18 for RedHat 6.2 (the kernel patches applied could in fact
be different enough to matter)?
These are all hypothetical examples, of course -- but Linux is not the
only platform that has these versioning problems just waiting to bite.
Linux probably has more of them than most, but it is not alone in having
them.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
re are other more capable packages out
there, but Netscape works the same on Win9x and Linux, both of which are
in use on my notebook.
I have to keep up, or the e-mail flood after a couple of days is just
about unbearable.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
that I get the contrib stuff in beta5's
RPMset -- I will attempt to do that, but I'm making no guarantees at
this point.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
something
cleaner -- compatible, but cleaner. I'll have to research what the
defaults are for later RH's -- but, as 6.1 is one of my target platforms
at this time, I have to fix that issue for sure.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-
RC=$?
[ $RC -eq 0 ] && success "$base $killlevel" || failure "$base
$killlevel"
fi
fi
Is 6.1 this different from 6.2? This code on the surface seems
reasonable to me -- am I missing something? The 6.2 code (found i
my RH _4_.1 CD, but that's just
a _little_ old :-).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
where it doesn't, blame Red Hat. :-)
So we're going to credit Linux for PostgreSQL being shipped as part of
the RedHat distribution since RH 5.0, then? :-0
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 2:
MIPS for such a purpose)? The last thing I want to do is
wait too long on some platforms and not long enough on others.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send a
Tom Lane wrote:
> The tricky part of this is not to give up the ability to restart when
> there *has* been a crash.
But kill -9 effectively _is_ an admin-initiated crash.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)-
postmaster coming up and try to
'sync up' with that postmaster, like the baroque GEMM handshake dance
performed by 386 memory managers when Windows needs to start its own
VMM?
Or should we spend that much time protecting Barney Fife's from their
own single bullet? :-)
Just a nor-easter
al solution is elsewhere, anyway. I just have to make
sure it is not data-corruption broken. And, if leaving the -9 out
completely is the only solution, then, well, it's the only solution.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)
that day? :-) I certainly have no problem using pg_ctl for this purpose
-- as I have been using pg_ctl to start postmaster all along (then why
am I not using it to stop -- don't answer that :-))..
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---
Tom Lane wrote:
> Lamar Owen wrote:
> > Postmaster can easily enough find out if zombie backends are 'out there'
> > during startup, right?
> If you think it's easy enough, enlighten the rest of us ;-).
If postgres reported PGDATA on the command line it wo
e
backends I'll have to experiment. But not tonight -- last week was
more taxing than I thought. :-(.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an approp
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> If you think it's easy enough, enlighten the rest of us ;-).
> > If postgres reported PGDATA on the command line it would be easy enough.
> In ps status you mean? I don
the grim reaper
yank them in the wrong order for you, in any case.
--
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])
Peter Eisentraut wrote:
>
> Lamar Owen writes:
>
> > I missed something somehwere: wasn't the consensus a few weeks ago that
> > pg_ctl shouldn't be used for a system initscript?
>
> The consensus(?) was that there was some work to do in pg_ctl before i
--
I am going to sleep 1 and loop sixty times) -- no need to unnecessarily
delay system shutdown (and potential restart). And I won't put in the
-KILL unless I can find a safe and thorough way to do so.
Or I may go ahead and pg_ctl-ize things and let pg_ctl do the dirty
en. Should be fixed in the latest public beta
of RedHat, that actually has the 2.4 kernel. I can't really say any
more about that, however.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 2: you can get off a
ry here? At least they are payrolling
Second Chair on the Linux kernel hierarchy. And they are very
supportive of PostgreSQL (by shipping us with their distribution).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3
ndards, has had a brown paper bag release --
we all still make mistakes (I know -- I've made more than my share of
them).
Anyway, that's more than what the rest of the list wanted to read.
Replies to private e-mail, please.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-
ter, even if it is
masking a certain amount of shortsightedness on a certain initscripts
author's part. :-)
--
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 com
.
See the thread starting at
http://www.postgresql.org/mhonarc/pgsql-hackers/2000-03/msg00107.html
for details.
(And the search is working :-)).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Been far too busy for my own good here at work in the last three weeks
to touch RPM stuff.
This set will be built on both RH 7 and RH 6.2, if I can swing it. More
to follow. Pray for snow in Western North Carolina :-).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(
RPM's, or will it be a day or two before RC1?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
*** ./expected/temp.out Sat Jan 8 22:48:39 2000
--- ./results/temp.out Tue Mar 20 16:06:10 2001
***
*** 23,32
(1 row)
DROP TABLE temptest;
SELECT * FROM temptest;
col
--
On Tue, 20 Mar 2001, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > DROP TABLE temptest;
> > + NOTICE: FlushRelationBuffers(temptest, 0): block 0 is referenced (private 0,
>global 1)
> > + ERROR: heap_drop_with_catalog: FlushRelationBuffers r
On Tue, 20 Mar 2001, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > DROP TABLE temptest;
> > + NOTICE: FlushRelationBuffers(temptest, 0): block 0 is referenced (private 0,
>global 1)
> > + ERROR: heap_drop_with_catalog: FlushRelationBuffers returned
rs are you using --- -B and so forth?
Default. To be changed before RPM release, but currently it is the default.
The only option that postmaster.opts records is -D, and I'm not passing
anything else.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast
now much more leery of our regression suite -- this issue isn't
even tested, in reality. Do we have _any_ WAL-related tests? The parallel
testing is a good thing -- but I wonder what boundary conditions aren't getting
tested.
--
Lamar Owen
WGCR Internet Radio
1 Pe
to hub.).
Tomorrow morning, if I can get out of the snow-covered driveway and to work, I
can upload it much quicker.
I'll go ahead and upload the one I'm testing with right now if you'd like.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast
the regression failure that subsequently took the rest of the
afternoon to track.
Before final release I have a rewrite of the README to do, as well as a full
update of the migration scripts for testing.
I'm looking at /usr/lib/pgsql/contrib/* for the contrib stu
; Linux 2.2.16 x86 7.1 2001-03-19, Thomas Lockhart
Did you get the message from Trond about Linux 2.4 x86? I can also
verify all tests passed on a RedHat Public Beta installation with kernel
2.4.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
--
Trond Eivind Glomsrød wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Did you get the message from Trond about Linux 2.4 x86? I can also
> > verify all tests passed on a RedHat Public Beta installation with kernel
> > 2.4.
> I haven't put those in the lis
release -- and I plan on working
a while this Saturday on that -- but my week is so loaded that I'm going
to put out a rebuild of 7.1beta6->7.1RC1 as is -- once I get it to
build.....
Stay tuned...
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)-
Lamar Owen wrote:
>
> Mike Cannon-Brookes wrote:
> >
> > Any change of getting a 7.1 RC1 RPM? I'm using the beta4 RPMs at the moment
> > but don't seem to be any more recent ones.
>
> I'm building a quickie RC1-1 RPM right now. There are some oth
Lamar Owen wrote:
> Well, in any case, preliminary 7.1RC1 RPMS are up. There are some odd
> issues with the packaging that I am working on. Be sure to read
> README.rpm-dist -- attached to this message for your convenience.
Forgot to attach the file. :-(.
--
Lamar Owen
WGCR Interne
tp site right now for ODBC is
broken. I'll fix it tonight or tomorrow -- and the source RPM won't
rebuild on RH 6.2. I'll upload a -2 set tonight or tomorrow to fix
that, and a few other issues I found while dinking with it today.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---
ve to trace the build
in detail. And the html docs tree is going to the wrong place...
In any case, a unified or context diff against the 7.1beta4 spec would
be useful.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Hiroshi Inoue wrote:
> Lamar Owen wrote:
> > H. Hiroshi committed an update to GNUmakefile to 'enable multibyte
> > support' for ODBC. But that was only 33 hours ago -- meaning it wasn't
> > updated in time for RC1. Lessee. I'm rebuilding RC1
matter. 'Indexes' is just fine. It's
certainly a better plural than 'Vaxen' was in its time; although I am
still inclined to use 'boxen' when referring to more than one computer.
--
Lamar Owen
WGCR Internet Radio
Professor of English, Anchor Baptist Bib
On Thursday 13 February 2003 20:09, Bruce Momjian wrote:
> Lamar Owen wrote:
> > This isn't the same environment, Bruce, that you got into back when it
> > was still Postgres95.
> So you are saying this isn't my grandma's database anymore. :-)
I actually t
involved now (I know the historical reason)?
Comments?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
301 - 400 of 513 matches
Mail list logo
