/101041201.asp
He seems to be ok on some things, though.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Hat 7.1 is _nice_. The PostgreSQL speed appears to be very good,
compared to 6.2/7.0 with the 2.2 kernel.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
for the weekend, and hasn't read any responses yet.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
. Gotta learn it a little
--
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
recommend pgsql-cygwin,
lest someone erroneously think we directly support Win32.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
to
know some details of the trees occasionally. I'm sure Oliver would
agree.
And, to let everyone know, I'm having a blast doing this. And I'm glad
my work schedule eased up some in the last month so I could put some
time to this task.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
http://www.crn.com/Sections/Fast_Forward/fast_forward.asp?ArticleID=25670
Marc will be pleased to note that the PostgreSQL project came out of the
FreeBSD project, and is Great Bridge's database. Gotta love
journalistic license.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
RedHat 7.0 -- isthat an acceptable JDK-substitute?) or someone needs to
package 7.1 JDBC jars for my packaging pleasure. I'm running low enough
on disk space on my devel machines (one of which is a notebook) to make
my own JDK a second choice.
Oliver, what are doing with the JDBC client?
--
Lamar
On Fri, 13 Apr 2001, Peter Eisentraut wrote:
Lamar Owen writes:
In the postgresql-docs subpackage, along with the SGML source.
Why would you want to ship the source?
For those with SGML tools and viewers, who might like to build hardcopy of
their own. Frankly, it was an easy thing to do
version if the need arises.
Otherwise, enjoy the RPMset :-)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
README.rpm-dist
-
Version 3.2, for PostgreSQL 7.1
Lamar Owen [EMAIL PROTECTED]
Updated by [EMAIL PROTECTED
Peter Eisentraut wrote:
Lamar Owen writes:
One quick note -- since 'R' 'b', the RC RPM's must be forced to
install with --oldpackage, as RPM does a simple strcmp of version
numbers -- 7.1RC3 7.1beta1, for instance. Just force it with
--oldpackage if you have a 7.1beta RPM already
Oliver Elphick wrote:
Lamar Owen wrote:
as the Debian packages have the same issue -- and I don't know if .deb
has an analog to Serial:.
We have epochs, that is, the package version is preceded by an integer
and a colon, which overrides every other part of the version and release
Peter Eisentraut wrote:
Lamar Owen writes:
Yes, I am, actually. But it seems a broken way of dealing with it.
Although I do have another idea, thanks to Trond. Rather than package
'7.1RC4-1' I could package '7.1-0.1RC4' -- giving a straight
versioning. I could progress from '7.1
have a good JDK on any of my devel boxen --
meaning I'm still shipping the 7.0 JDBC in the jdbc subpackage.
ftp://ftp.postgresql.org/pub/dev/test-rpms,as usual. See
README.rpm-dist in the main package for more details, as it is actually
up to date at this time.
--
Lamar Owen
WGCR Internet Radio
1
of the rpm build system, on
distributions that do buildrootpolicies, which are standard in late
3.0.x RPM as well as 4.x RPM. This is one of the reasons the %{_mandir}
macro is used for all man pages.
Thanks for taking the time to look (again).
--
Lamar Owen
WGCR Internet Radio
1
then a 7.0.4 that fixes bugs in the STABLE branch,
whereas at one point Linux 2.0.39, a 2.2.x, and 2.4.0 were being
released concurrently. The same happens with FreeBSDand others -- but
not us.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast
/access/itup.h
[root@utility i386]#
--
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
--
we'll see what I find in a few hours.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the timing.
--
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
the individual packages instead of
the great big one) so from a packaging perspective, its well tested ...
Just not well-tested for the RPM build environment :-).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 6: Have you
in the main package.
--
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
The Hermit Hacker wrote:
On Sat, 7 Apr 2001, Lamar Owen wrote:
Just not well-tested for the RPM build environment :-).
Ya, but you could concievably test that now, without us doign an RC4 ..
the files are all there :)
So the structure isn't going to change -- just there's not going
-- well,
actually, I just want to make sure I get it right before release, as I'd
like to not have but a couple of days before an RPM release after the
announcement.
Sounds like a plan.
I'm going to upload a set of RC3 RPM's tonight -- there are changes that
I need people to comment upon.
--
Lamar
Uploaded. Please take a look.
ftp://ftp.postgresql.org/pub/dev/test-rpms
There _are_ changes. I will detail the changes for the RC4 RPMset.
Karl's pl/perl changes will go into the next set. pg_dumplo will have a
built binary, to be located in /usr/lib/pgsql/contrib.
--
Lamar Owen
WGCR
in the main
package %doc.
HTML docs and man pages are with the main package; SGML source and any
hardcopy docs will go into the docs subpackage. The contrib tree is
getting its own subpackage.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast
One quick note -- since 'R' 'b', the RC RPM's must be forced to
install with --oldpackage, as RPM does a simple strcmp of version
numbers -- 7.1RC3 7.1beta1, for instance. Just force it with
--oldpackage if you have a 7.1beta RPM already installed.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4
' document is still in the main package, FWIW.
--
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
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)---
TIP 6: Have
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 other things
I need to do on the RPMset before final release
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 Internet Radio
1 Peter
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
---(end of broadcast)---
TIP 1
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
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
---(end of broadcast)---
TIP 4
Trond Eivind Glomsrd 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 list yet... I'll wait until we release a
product
, 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
-
!1
(1
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 -2
SELECT * FROM temptest;
Hoo
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 -2
SELECT * FROM temptest;
Hoo
. 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)---
TIP 5: Have you checked our
-- 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 Peter 4:11
---(end of broadcast
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)---
TIP 5: Have you checked our
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 stuff.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end
/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
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 it
was robust enough to be used (for anything
(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
work, as that IS what pg_ctl is supposed to accomplish.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
ublic 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 all lists at once with the unregister command
(send &
? 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: if posting/reading
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
---(end of broadcast
ain 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 command
(send "unregister YourE
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
---(end of broadcast
s code on the surface seems
reasonable to me -- am I missing something? The 6.2 code (found in
/etc/rc.d/init.d/functions, for those who might not know where to find
killproc) sets a default killlevel but never uses it -- ignorant but not
stupid.
--
Lamar Owen
WGCR Internet Radi
, 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]
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: you can get off all lists at once with the unregister
s
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 an appropriate
subscribe-nomail command to [EMAIL PRO
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)---
TIP 2
, 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 of a brainstorm
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
s 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)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
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
---(end of broadcast
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 would be easy enough.
What can postmaster
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 appropriate
subscribe-nomail command to [EMAIL PRO
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't think we are prepared to require ps
status
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])
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
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
at cleaning the old out.
Sometimes a little too good :-/.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-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.
The select_views delta looks like a sort
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
ut, 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() is buggered to use the
locale's collation.
The real solution is for the vendors to fix their broken locales.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
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 ever been:
[snip]
Is that the code after any
mucking around with
the core, particularly this close to release.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
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 in that, I can tackle doing this. Don't know
if I can do so before 7.1 release, but I'll certainly try.
--
Lamar Owen
WGCR Intern
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
will do the legwork to make the list.
Count me as liking it.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
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
!)
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
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.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
headers (no
duplicates) (again, expounding upon what Tom said already).
Comments?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
ing 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
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:
[...]
Doesn't seem like it saves enough
: 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
' 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 Glomsrd wrote:
Lamar Owen [EMAIL PROTECTED] writes:
Trond Eivind Glomsrd wrote:
Not to sound scheptical, but since when did postgresql care about
backwards compatiblity? Upgrading is already demanding a lot of
Upgrading is only one facet of backwards compatibility.
I
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/postgresql.conf file that is read
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 spelled PGHOST as of 7.1
g 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 TCP/IP hostname,
which PGHOST is, right
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 postmaster --- it must figure out *on its
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 available, it varies in parameters
I said
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 were _not_
built
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
for 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, the lock file is put
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
vice versa. Also, the name
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
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
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 course.
But, Peter's point does hold -- someone will have to maintain this.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
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 and development
RPM's you need from there.
--
Lamar Owen
WGCR Intern
301 - 400 of 460 matches
Mail list logo
