On 12/2/2004 8:16 PM, Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
One more issue. Until we start RC, patches that are bug fixes will
continue to be applied. Do we want that? By going RC we are basically
saying we need to focus on docs and packaging and we
Bruce Momjian [EMAIL PROTECTED] writes:
TODO item?
Sure:
* ANALYZE should record a pg_statistic entry for an all-NULL column
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
On Sun, 28 Nov 2004 17:53:38 -0500, Tom Lane wrote:
But is it cheaper, IO-wise to jump around in an index than to go back
and forth between index and tuple blocks?
Perhaps not --- but why would you be jumping around? Wouldn't the
needed info appear in consecutive locations in the index?
Troels Arvin [EMAIL PROTECTED] writes:
How much of[1] is still the case today?
Reference 1:
Stonebraker Olson: Large Object Support in POSTGRES (1993)
http://epoch.cs.berkeley.edu:8000/postgres/papers/S2K-93-30.pdf
Probably almost none of it ... the only thing I know about the
Berkeley-era
On 12/2/2004 3:18 AM, Thomas Hallgren wrote:
Jan,
... plus that the catch-nesting automatically represents the
subtransaction nesting. I can't really see any reason why those two
should not be bound together. Does anybody?
That depends on what you mean. As a stop-gap solution, cerntanly. But in
On Fri, Dec 03, 2004 at 01:35:55PM -0300, Alvaro Herrera wrote:
In pg_restore --help I see this:
-O, --no-owner do not output commands to set object ownership
[...]
-x, --no-privileges skip restoration of access privileges
(grant/revoke)
Sorry, of course the problem is
On Thu, Dec 02, 2004 at 08:34:11PM -0600, Jim C. Nasby wrote:
I've tried emailling David Fetter to no avail; anyone know who's in
charge of the torrents or anyone who can answer my original
question?
I'm in charge, and re: your original question, perhaps some creative
use of wget could help.
People,
In pg_restore --help I see this:
-O, --no-owner do not output commands to set object ownership
[...]
-x, --no-privileges skip restoration of access privileges (grant/revoke)
Do we talk about output commands to do things, or directly about
restoration? I think -O
I just compiled 8.0beta5 on my old Sparc 5. All tests passed. This
is running Debian 3.0 with a 2.2.20 kernel. Sure took a long time. :)
I can test on an ia32/RedHat 6.2 machine if that would be helpful.
-Doug
---(end of broadcast)---
TIP 2:
Patch applied. Thanks.
---
Andrew Dunstan wrote:
I wrote:
If it bothers you that much. I'd make a flag, cleared at the start of
each COPY, and then where we test for CR or LF in CopyAttributeOutCSV,
if
OK, where are we in the release process? We still have a few open
items, but those can be moved to the TODO list. Do we do RC1 or Beta6?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive,
Alvaro Herrera [EMAIL PROTECTED] writes:
Do we talk about output commands to do things, or directly about
restoration? I think -O description should be
-O, --no-owner skip restoration of object ownership
This seems reasonable, but I wonder whether we should hold it for 8.1.
There
Jan Wieck wrote:
There is no try in Tcl.
The syntax is
catch { block-of-commands } [variable-name]
Catch returns a numeric result, which is 0 if there was no exception
thrown inside of the block-of-commands. The interpreter result, which
would be the exceptions error message in cleartext, is
On Fri, Dec 03, 2004 at 12:20:51PM -0500, Tom Lane wrote:
This seems reasonable, but I wonder whether we should hold it for 8.1.
There hasn't been any official declaration that translatable strings
are frozen for 8.0 --- but are we at that point yet? Even if we're
not at hard freeze, minor
Bruce Momjian wrote:
OK, where are we in the release process? We still have a few open
items, but those can be moved to the TODO list. Do we do RC1 or
Beta6?
Considering all the patching that has been going on recently and the
fact that we don't have any port reports, I think it's too early
Peter Eisentraut wrote:
Bruce Momjian wrote:
OK, where are we in the release process? We still have a few open
items, but those can be moved to the TODO list. Do we do RC1 or
Beta6?
Considering all the patching that has been going on recently and the
fact that we don't have any port
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Do we talk about output commands to do things, or directly about
restoration? I think -O description should be
-O, --no-owner skip restoration of object ownership
This seems reasonable, but I wonder whether we should
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
OK, where are we in the release process? We still have a few open
items, but those can be moved to the TODO list. Do we do RC1 or
Beta6?
Considering all the patching that has been going on recently and the
fact that we don't have
Peter Eisentraut [EMAIL PROTECTED] writes:
Change it right now, and then we'll freeze. :)
Done.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Fri, 3 Dec 2004, Peter Eisentraut wrote:
Bruce Momjian wrote:
OK, where are we in the release process? We still have a few open
items, but those can be moved to the TODO list. Do we do RC1 or
Beta6?
Considering all the patching that has been going on recently and the
fact that we don't have
On December 3, 2004 10:31 am, you wrote:
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
OK, where are we in the release process? We still have a few open
items, but those can be moved to the TODO list. Do we do RC1 or
Beta6?
Considering all the patching that has been
On 12/3/2004 12:23 PM, Thomas Hallgren wrote:
Jan Wieck wrote:
There is no try in Tcl.
The syntax is
catch { block-of-commands } [variable-name]
Catch returns a numeric result, which is 0 if there was no exception
thrown inside of the block-of-commands. The interpreter result, which
would be the
Darcy Buskermolen [EMAIL PROTECTED] writes:
On December 3, 2004 10:31 am, you wrote:
2. There are critical notices on buildfarm for some more popular
platforms such as Solaris 9 and Open BSD.
The OpenBSD error should be fixed by
Jan Wieck [EMAIL PROTECTED] writes:
Your suggestion to expose a plain savepoint interface to the programmer
leads directly to the possiblity to commit a savepoint made by a
sub-function in the caller and vice versa - which if I understood Tom
correctly is what we need to avoid.
If we
On Dec 3, 2004, at 2:04 PM, Jan Wieck wrote:
[snip]
The point we where coming from was Tom's proposal to wrap each and
every single SPI call into its own subtransaction for semantic
reasons. My proposal was an improvement to that with respect to
performance and IMHO also better matching the
James Robinson [EMAIL PROTECTED] writes:
The JDBC interface exposes the savepoint interface, via setSavepoint(),
releaseSavepoint(), and rollback(Savepoint sp) methods on the
Connection, and Thomas's design of PL/Java offers the SPI via mapping
it onto JDBC. Would client-side JDBC also
Joshua D. Drake [EMAIL PROTECTED] writes:
1. Buildfarm doesn't yet have that many platforms on it.
It's not as bad as all that. Our current list of supported platforms
(ie, things that got tested last time) is
AIX
Free/Open/NetBSDcovered by buildfarm
HPUX
Tom Lane wrote:
Where the buildfarm falls down a bit is on the cross-product
coverage. But I think you're not going to get the cross product
without a call for port reports; there aren't that many people who
are going to offer dedicated time on every random platform there is.
Once RC1 is out
On Fri, Dec 03, 2004 at 03:20:48PM -0500, Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
1. Buildfarm doesn't yet have that many platforms on it.
It's not as bad as all that. Our current list of supported platforms
(ie, things that got tested last time) is
AIX
Peter Eisentraut [EMAIL PROTECTED] writes:
Does the build farm turn on all the
compiler options? It really should. I'm looking for
/configure --prefix=SOMEWHERE --enable-thread-safety --with-tcl \
--with-perl --with-python --with-krb5 --with-pam -with-openssl
I was just thinking about
Jan Wieck wrote:
as you now suggest? I don't remember suggesting that. I concluded
from your statements that _you_ are against changing Tcl's catch but
instead want the savepoint functionality exposed to plain Tcl. So
_you_ are against _my_ suggestion because these two are mutually
exclusive.
Tom Lane wrote:
It's too bad the buildfarm reports don't show more details about what
CVS pull they're using exactly.
Snapshot is the UTC time at which the cvs pull was done. Clients report
what files have changed since the last run, and also, in the case of a
failure, what files have
Tom/all,
I have setup the following running debian linux. MIPS, MIPSEL, ALPHA, PARISC,
M68K, ARM, SPARC, I386. I have the
build farm running local and I have just started to get the systems registered.
I am also willing to aquire other
hardware/ operating systems in an effort to give
Approx ... but, if anyone has anything they want to say before that
happens, you have an hour left to god save your souls *muhahahaha*
Okay, not that bad ... but, just figured I'd give a heads up in case
someone was just finishing off something ...
Marc G. Fournier Hub.Org
template2=# SELECT version();
version
--
PostgreSQL 8.0.0beta5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
3.4.2 (Debian 3.4.2-3)
(1 row)
template2=# CREATE
Peter Eisentraut wrote:
Tom Lane wrote:
Where the buildfarm falls down a bit is on the cross-product
coverage. But I think you're not going to get the cross product
without a call for port reports; there aren't that many people who
are going to offer dedicated time on every random platform
On December 3, 2004 11:14 am, Tom Lane wrote:
Darcy Buskermolen [EMAIL PROTECTED] writes:
On December 3, 2004 10:31 am, you wrote:
2. There are critical notices on buildfarm for some more popular
platforms such as Solaris 9 and Open BSD.
The OpenBSD error should be fixed by
Hi *,
is somebody working on these two issues on the TODO-List?
1) Prevent default re-use of sysids for dropped users and groups
Currently, if a user is removed while he still owns objects, a new
user given might be
given their user id and inherit the previous users objects.
2) Prevent
Andrew Dunstan wrote:
I think that this case might be fixed
by the tweaking I did yesterday, but I can't tell whether that run
occurred before or after that commit. In any case it's not a real
failure, just an output-ordering difference.
I am running it again to see. I agree that at worst it
Andrew Dunstan [EMAIL PROTECTED] writes:
The configuration is chosen in the config file for each member, rather
than being dictated centrally.
This is good. Now what we need is a little cooperation among the
buildfarm team to make sure that the collective set of cases tested
covers all the
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
It's too bad the buildfarm reports don't show more details about what
CVS pull they're using exactly.
Snapshot is the UTC time at which the cvs pull was done.
That's good but it's of limited use to me, since the snaps are (I
presume)
Jim Buttafuoco [EMAIL PROTECTED] writes:
I have setup the following running debian linux. MIPS, MIPSEL, ALPHA,
PARISC, M68K, ARM, SPARC, I386. I have the build farm running local
and I have just started to get the systems registered.
Excellent, that's very good news.
Darcy Buskermolen [EMAIL PROTECTED] writes:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lorisdt=2004-12-03%2020:54:53
Lends me to think your tweek didn't push hard enough in the right spots.
Yup, you're right. I used a bigger hammer ;-)
regards, tom lane
On Dec 3, 2004, at 2:33 PM, Kenneth Marshall wrote:
On Fri, Dec 03, 2004 at 03:20:48PM -0500, Tom Lane wrote:
PPC tested pretty often by moi
RS6000 isn't this same as PPC?
This is the IBM Power4 and now Power5 architecture which is
different
On Fri, 3 Dec 2004, Tom Lane wrote:
That's good but it's of limited use to me, since the snaps are (I
presume) against the anonymous-CVS server which lags commits on the
master by I'm-not-sure-how-much.
19 * * * * /projects/update_anoncvs.sh
Marc G. Fournier Hub.Org Networking
Travis P [EMAIL PROTECTED] writes:
You'll probably find multi-OS-testing (various versions of AIX, Linux,
MacOS X on PPC and/or PowerPC) much more important than differentiating
particular pieces of hardware in the PPC or RS6000 category, assuming
both 32-bit and 64-bit is covered and also
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
It's too bad the buildfarm reports don't show more details about what
CVS pull they're using exactly.
Snapshot is the UTC time at which the cvs pull was done.
That's good but it's of limited use to
schmidtm [EMAIL PROTECTED] writes:
is somebody working on these two issues on the TODO-List?
1) Prevent default re-use of sysids for dropped users and groups
I don't know of anyone actively working on it, but if you check the
archives you'll find that the preferred solution approach is pretty
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this evening baring any 'its
broken' commends ;)
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!:
On Fri, 3 Dec 2004, Tom Lane wrote:
2) Prevent dropping user that still owns objects, or auto-drop the
objects
No one has any idea how to do this reasonably --- the problem is you
have no visibility into databases other than the one you're connected
to, so you can't tell what the user
Leading up to the release of PostgreSQL 8.0, the development group has
agreed to freeze the message strings, so now is the right time to send
in message translations for the 8.0 release. See
http://developer.postgresql.org/~petere/nlsinfo/
for information on how to contribute.
If there
Kris Jurka [EMAIL PROTECTED] writes:
On Fri, 3 Dec 2004, Tom Lane wrote:
No one has any idea how to do this reasonably --- the problem is you
have no visibility into databases other than the one you're connected
to, so you can't tell what the user owns in other databases.
What about Alvaro's
Marc G. Fournier [EMAIL PROTECTED] writes:
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this evening baring any 'its
broken' commends ;)
Tarball looks alright to me.
regards, tom lane
While monkeying around with configure --prefix I fond the following. (there
may be more but this one was still in my scroll back...
[...snip..]
/usr/local/bin/gmake -C ecpglib install
gmake[4]: Entering directory `/usr/local/src/postgresql-8.0.0/src/interface
s/ecpg/ecpglib'
gcc -O2
Darcy Buskermolen [EMAIL PROTECTED] writes:
While monkeying around with configure --prefix I fond the following.
You probably shouldn't backslash the space.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to
Kris Jurka wrote:
On Fri, 3 Dec 2004, Tom Lane wrote:
2) Prevent dropping user that still owns objects, or auto-drop the
objects
No one has any idea how to do this reasonably --- the problem is you
have no visibility into databases other than the one you're connected
to, so
Tom Lane wrote:
Darcy Buskermolen [EMAIL PROTECTED] writes:
While monkeying around with configure --prefix I fond the following.
You probably shouldn't backslash the space.
Also recall that we have just gone through some pain so we can make a
postgres installation relocatable. One of
On Fri, 3 Dec 2004, Bruce Momjian wrote:
What about Alvaro's shared dependencies work:
http://archives.postgresql.org/pgsql-hackers/2004-10/msg00963.php
That is for allowing comments on global tables like pg_shadow and
pg_database. I don't think it relates to finding if someone owns
Kris Jurka wrote:
On Fri, 3 Dec 2004, Bruce Momjian wrote:
What about Alvaro's shared dependencies work:
http://archives.postgresql.org/pgsql-hackers/2004-10/msg00963.php
That is for allowing comments on global tables like pg_shadow and
pg_database. I don't think it
I wrote:
I started work today on a page that lists all the members.
Now viewable here:
http://www.pgbuildfarm.org/cgi-bin/show_members.pl
In due course, the branch names will be links to the build history.
cheers
andrew
---(end of broadcast)---
TIP
Out of all of the messages on this thread, I am still not sure...
Is there an RC1 coming out RSN?
Lorne
--
---
[EMAIL PROTECTED]
---
---(end of
[EMAIL PROTECTED] wrote:
Out of all of the messages on this thread, I am still not sure...
Is there an RC1 coming out RSN?
Yes, it has been packaged and is now propogating to the mirrors. It is
on the main ftp site now under /pub/beta/*rc1*.
--
Bruce Momjian|
CONGRATULATIONS
BTW - I have the OS/2 port running through to creating the template0 and
template1 databases with initdb. I have a glitch with the fork()
processing that seems to be in the OS/2 GCC 3.3.5 runtime, but I expect to
have that resolved shortly.
I am going to apply the patches
As promised, I've posted 8.0.0rc1 rpms here:
http://www.joeconway.com/postgresql-8.0.0rc/
Again note that these are not official PGDG rpms, just my own home brew.
In addition to the change of Postgres itself from beta5 to rc1, I
updated jdbc to latest beta (pg80b1.308*).
Joe
64 matches
Mail list logo
