On Wed, Feb 28, 2007 at 02:20:01AM -0500, Tom Lane wrote:
Hiroshi Saito [EMAIL PROTECTED] writes:
Is this message necessary for setting errno again?
AFAIR we only intended that message as a temporary measure until we'd
figured out why things seemed to be failing on Windows. If there's no
Hi,
I think now this is really the final version.
Changes in this version is:
- when dropping a column that's referenced
by a GENERATED column, the GENERATED
column has to be also dropped. It's required by SQL:2003.
- COPY table FROM works correctly with IDENTITY
and GENERATED columns
-
Not that I think that anyone owning both a law degree and a computer
in 2007 should legitimately be able to plead innocence here. FAST
Australia's lawyers are making themselves look like idiots, and the
same for every other company tacking on such notices. I think the
real bottom line
I've updated the patch against Tom's recent commit of the SET_VARSIZE changes.
It's about 40% the size it was before, most of the remaining patch is actually
heaptuple.c and tuptoaster.c which is the key code.
http://community.enterprisedb.com/varlena/patch-varvarlena-13.patch.gz
I had fixed
On Wed, Feb 28, 2007 at 09:04:58AM +0100, Magnus Hagander wrote:
On Wed, Feb 28, 2007 at 02:20:01AM -0500, Tom Lane wrote:
Hiroshi Saito [EMAIL PROTECTED] writes:
Is this message necessary for setting errno again?
AFAIR we only intended that message as a temporary measure until we'd
On Tue, Feb 27, 2007 at 11:17:44AM -0800, Chris Marcellino wrote:
So I've finished reformulating this patch to use the device/inode
instead of the hash idea I had earlier.
I have tested this patch (on Darwin) to permit the postmaster to
recover after a crash or killing, and it will not
Messages with PDF's seem to be dropped as Magnus described yesterday.
It is in this tarball though:
http://homepage.mac.com/cmarcellino/postgres-posix-shmem.tar
As Tom has said a few times, there is an issue with the need to keep
two different lifecycles of postmasters and backends out of
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
Global Development Group the non-revokable right to
Joshua D. Drake wrote:
Bruce Momjian wrote:
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
Bruce Momjian wrote:
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
Global Development Group the
Bruce Momjian [EMAIL PROTECTED] writes:
Joshua D. Drake wrote:
We should add this to the mailing list signup pages and the welcome
pages to the lists.
Yep, good idea. Marc?
For -patches and -hackers, I agree. It seems a bit legalistic and
off-putting for the general lists, though.
On Wed, 21 Feb 2007 09:10, Bruce Momjian wrote:
Hi,
Following up this patch with a contribution statement.
'With permission from the Managing Director, Fujitsu Australia Software
Technology, I am granting the PostgreSQL Global Development Group the
non-revokable right to distribute the source
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Patric Bechtel [EMAIL PROTECTED] writes:
Maybe you want to have a look here:
http://www2.hursley.ibm.com/decimal/DPDecimal.html
Well we're not really looking for the optimal packing in general. All the
problems here have to do with convenience in the implementation rather than
the problems
On Thu, 1 Mar 2007 04:28, Bruce Momjian wrote:
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
Global
FAST PostgreSQL wrote:
On Thu, 1 Mar 2007 04:28, Bruce Momjian wrote:
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregory Stark schrieb am 01.03.2007 10:23:
Patric Bechtel [EMAIL PROTECTED] writes:
Maybe you want to have a look here:
http://www2.hursley.ibm.com/decimal/DPDecimal.html
Well we're not really looking for the optimal packing in general. All the
On Wed, 28 Feb 2007, Bruce Momjian wrote:
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
Here's a patch that works with
Bruce Momjian [EMAIL PROTECTED] writes:
I have coded up the following patch which places LOG just above ERROR in
log_min_error_statement.
LOG_NO_STATEMENT? What *are* you thinking? The kindest word I can find
for this is baroque.
What I had in mind was a one-line patch:
if
Michael Glaesemann schrieb am 01.03.2007 12:41:
On Mar 1, 2007, at 12:32 , Patric Bechtel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregory Stark schrieb am 01.03.2007 10:23:
Patric Bechtel [EMAIL PROTECTED] writes:
Maybe you want to have a look here:
23 matches
Mail list logo