-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
Sent: 20 January 2004 00:21
To: Lamar Owen; [EMAIL PROTECTED]
Subject: Re: [HACKERS] Old binary packages.
Lamar Owen wrote:
I am looking at the possibility of cleaning up the binary
tree on the
ftp site,
On Monday 19 January 2004 19:35, Lamar Owen wrote:
What I was thinking would be to remove all but the last minor release of
each major version. Thus, I would remove 7.4, but leave 7.4.1.
Perhaps check the download figures for each first?
--
Richard Huxton
Archonet Ltd
Dann Corbit wrote:
When replication is implemented, what is going to happen with database
systems that rely heavily on sequences for primary keys?
Don't know which replication system you mean, there are some implemented
already.
As for Slony, I plan to have the functions setval(), nextval() and
On Monday 19 January 2004 03:53 pm, Tom Lane wrote:
Lamar Owen [EMAIL PROTECTED] writes:
I am looking at the possibility of cleaning up the binary tree on the ftp
site, and was wondering what the group thought about purging old
binaries. What I was thinking would be to remove all but the
Brian Moore [EMAIL PROTECTED] writes:
i would like to begin work on the TODO item
Allow backend to output result sets in XML
I am not sure why it's phrased that way --- surely the code to hack on
is the client side, not the backend. Otherwise you need a protocol
revision to make this happen,
On Mon, 19 Jan 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Just had a client point this out to me, and am wondering if its supposed
to happen:
420_test= select
dropgeometrycolumn('420_test','lroadline61','roads61_geom');
ERROR: permission denied for relation
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
When writing a PL/pgSQL trigger function how do you handle the case :
EXECUTE ''UPDATE test_table SET test_col '' ||
quote_literal(NEW.test_col2) || '';'';
Seems it'd be easier without EXECUTE:
UPDATE test_table SET test_col =
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 19 Jan 2004, Tom Lane wrote:
in particular, what SQL command is it trying to execute when it chokes?
The function is executing:
EXECUTE ''update pg_attribute set attnotnull = false from pg_class where
On Tue, 20 Jan 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 19 Jan 2004, Tom Lane wrote:
in particular, what SQL command is it trying to execute when it chokes?
The function is executing:
EXECUTE ''update pg_attribute set attnotnull = false from pg_class
Marc G. Fournier [EMAIL PROTECTED] writes:
So, if we replace that with:
ALTER TABLE table_name ALTER column_name DROP NOT NULL; ?
should be good to go? still not as clean as doing the straight DROP
COLUMN, but its a fast fix ...
Yeah, that's what I'd do until the PostGIS guys can rethink
Dear Lamar Owen ,
Since we are keeping
all source releases (although I would question that, since we use CVS),
keeping all the binaries around is just a space waster, IMHO.
Comments?
Keeping 7.X and then 7.X.y where y is the last minor version for 7.X is
fine
As you would have noticed
Josh Berkus wrote:
People,
I don't have the time to make enough different attempts to find the one
that pleases all. My argument still is that all this IO throttling and
IO optimizing is mainly needed for dedicated servers, because I think
that if you still run multiple services on one box
Lamar Owen wrote:
While disk may be cheap, it ain't so cheap that wasting it is a good
thing. With the source releases still available way back, havng
binaries that old, while useful to some, is not IMO in the best
interest of all.
But where are the spec files and other stuff that belongs
Hey all,
I hope this isn't off-topic or inapropriate to this list ...
I'm not familiar with the PostgreSQL patch-submittal/development cycle.
I recently submitted a patch regarding \copy syntax in psql, and I'd
like to keep an eye on it to see that it gets comitted, or respond if
there are
On Tuesday 20 January 2004 01:36 pm, Peter Eisentraut wrote:
But where are the spec files and other stuff that belongs into the old
RPMs? Just the source releases are not enough if someone needs to deal
with old systems. And since you mentioned it, creating a source
tarball from CVS does
Bill Moran [EMAIL PROTECTED] writes:
I sent the patch to [EMAIL PROTECTED] two days ago, and
have heard nothing in reply. Is this typical lag?
Right at the moment, incoming patches are a tad backed up because Bruce,
who usually handles them, is off traveling. I'm trying to fill the gap
a bit
Brian Moore wrote:
i would like to begin work on the TODO item
Allow backend to output result sets in XML
Implementing this on the client side seems cleaner (and is trivial to
implement). Some people have in fact already done that. Search the
archives.
---(end of
EXECUTE ''UPDATE test_table SET test_col '' ||
quote_literal(NEW.test_col2) || '';'';
Seems it'd be easier without EXECUTE:
UPDATE test_table SET test_col = NEW.test_col2;
Actually, yes you're right - we don't need EXECUTE in our case.
However, it still doesn't answer the question of how you
Merlin Moncure kirjutas E, 12.01.2004 kell 19:56:
Hannu Krosing wrote:
IIRC, the charset transformations are done as a separate step in the
wire protocol _before_ any parser has chance transform or not.
Yep. My point is that this is wrong.
Of course :)
We need this because our
19 matches
Mail list logo
