After installing the following into my msys/mingw set:
http://prdownloads.sourceforge.net/mingw/bison-1.875.0-2003.02.10-1.exe?download
and http://www.cs.colorado.edu/~main/mingw32/flex-2_5_4a.zip (Not sure if
this was needed, but I did it anyway) and then running
configure --without-zlib
Hi,
Are we going to address the fact that you can't enter 3 digit years without
a leading 0?
australia=# select '111-01-01'::date;
ERROR: Bad date external representation '111-01-01'
australia=# select '0111-01-01'::date;
date
0111-01-01
(1 row)
I can't see any reason why we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 15 September 2003 09:09, Christopher Kings-Lynne wrote:
Hi,
Are we going to address the fact that you can't enter 3 digit years without
a leading 0?
australia=# select '111-01-01'::date;
ERROR: Bad date external representation
I can't see any reason why we shouldn't allow it???
Works here(7.4beta2):
andreak=# select '111-01-01'::date;
date
-
0111-01-01
(1 row)
Ooooh - that must have been a side effect of the 'only parse dates in set
format' changes...was it intended?
Chris
I get the following errors
gmake -C ecpglib all
gmake[4]: Entering directory
`/usr/local/postgres/pgsql/src/interfaces/ecpg/ecpglib'
../../../../src/backend/port/aix/mkldexport.sh libecpg.a libecpg.exp
gcc -O2 -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -Wl,-bnoentry -
Hi all,
A user on IRC came across the following tuple concurrently updated error
when using LISTEN/NOTIFY intensively. The user managed to isolate the
problem and SQL generating the problem. A few sessions are required to
generate the error.
T1:
---
begin;
listen test;
commit;
T2:
---
begin;
Heads up: it appears that the Linux stable kernel series is about to get a
sane VM system from Andrea Arcangeli, which has proper page accounting and
does not have an Out Of Memory killer at all.
This will probably take a while to make its way into vendor kernels, and
even then we'll need to
On Mon, 15 Sep 2003, Tom Lane wrote:
Hm, dollar quoting doesn't sound too bad. I could go with that,
unless someone has a better idea?
I don't mind dollar quoting. How about block quoting? That describes
what it's used for, rather than what it looks like.
Jon
On Sat, 13 Sep 2003, Miko O'Sullivan wrote:
[EMAIL PROTECTED] (Jon Jensen) wrote in message news:[EMAIL PROTECTED]...
INSERT INTO sometable (5, \.
a
very long
string
\.
);
I'm delighted to hear that here docs are being discussed for postgres.
In the world of Perl here docs
Hello:
I'm testing the TLS support of my .net data provider for PostgreSQL 7.4
(on Cygwin using PostgreSQL 7.4 Beta 2), i have a question, i'm
receiving Application data messages with a length of 24 bytes than
decrypted are empty messages ( decrypted message length = 0 ), is this
correct
ivan wrote:
Is true, but sometimes programers needgood database engine for simply
program.I think that postgres is one of the best sql db for free and with
open source, [...]
Your current alternatives are:
- Firebird: can be built as an embedded database engine (may be
experimental)
- MySQL: can
sendmail.cf
Sean Chittenden wrote:
The $$FOO proposal I put forward earlier was consciously modeled on
here-documents.
Couldn't we allow at the beginning of the line to mean 'here' document?
No; you could easily be breaking existing queries, for example
Let me jump in for half a second here
Can we add digits to the allowed character set of the marker? It'd make
life easier for languages that check if the quoting marker actually
occurs in the text to be quoted.
Jan
Tom Lane wrote:
Sean Chittenden [EMAIL PROTECTED] writes:
Using $$[.*]\n as a lexical token is a quasi-problematic
On Mon, 2003-09-15 at 07:32, Andrew Dunstan wrote:
This will probably take a while to make its way into vendor kernels, and
even then we'll need to keep the warnings in the docs for people running
older kernels. I am not sure at this stage what its status is for the 2.6
kernel series.
The 2.6
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
I think calling it 'here-document' quoting is possibly unwise - it is
sufficiently different from here documents in shell and perl contexts to
make it confusing.
I agree. I've tried to think of a better alternative name, but without
much
quote-less quoting
:-)
Robert Treat
On Mon, 2003-09-15 at 02:38, Andrew Dunstan wrote:
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Hannu Krosing [EMAIL PROTECTED] writes:
Tom Lane kirjutas P, 14.09.2003 kell 18:58:
Those seem pretty unmemorable and
Jon Jensen wrote:
On Sat, 13 Sep 2003, Miko O'Sullivan wrote:
[EMAIL PROTECTED] (Jon Jensen) wrote in message news:[EMAIL PROTECTED]...
INSERT INTO sometable (5, \.
a
very long
string
\.
);
I'm delighted to hear that here docs are being discussed for postgres.
In the world of Perl
On Thu, 2003-09-11 at 11:57, Max Jacob wrote:
Hallo to everybody.
I have found out that statements in a function beheave differently than
root statements due to the fact that statements inside a function do
not update the db snapshot.
I already read the discussions in the archieve before
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Ooooh - that must have been a side effect of the 'only parse dates in set
format' changes...was it intended?
Yes, I thought so. The relevant bit of the change is here:
! /***
!* Enough digits to be unequivocal year? Used to test for 4
Just finished bundling it, so will give a few for the mirrors to pull it
in, but it is now available for download if ppl want to confirm its okay
...
I also removed the beta1 bundles, but have left the beta2 ones in place
...
---(end of
Neil Conway wrote:
On Mon, 2003-09-15 at 07:32, Andrew Dunstan wrote:
This will probably take a while to make its way into vendor kernels, and
even then we'll need to keep the warnings in the docs for people running
older kernels. I am not sure at this stage what its status is for the 2.6
Jon Jensen [EMAIL PROTECTED] writes:
On Sat, 13 Sep 2003, Miko O'Sullivan wrote:
In Perl, the rule for here docs is NOT it starts immediately after
the definition of the terminator (as in your example). The rule is
it starts on the first line after the end of the command in which the
On Thu, 2003-09-04 at 13:14, Kurt Roeckx wrote:
tablecmds.c: In function `validateForeignKeyConstraint':
tablecmds.c:3546: warning: dereferencing type-punned pointer will break
strict-aliasing rules
So, what should we do with this?
The recommended way to deal with is to put them into a
On Mon, 15 Sep 2003, Tom Lane wrote:
In Perl, the rule for here docs is NOT it starts immediately after
the definition of the terminator (as in your example). The rule is
it starts on the first line after the end of the command in which the
terminator appears. There's a very good reason
Jan Wieck [EMAIL PROTECTED] writes:
Can we add digits to the allowed character set of the marker?
We can't allow a digit right after the opening dollar sign; that would
look like a parameter.
I suppose we could allow $identifier$ though. That might be the easiest
compromise.
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
Can we add digits to the allowed character set of the marker?
We can't allow a digit right after the opening dollar sign; that would
look like a parameter.
I suppose we could allow $identifier$ though. That might be the easiest
Gavin Sherry [EMAIL PROTECTED] writes:
ERROR: tuple concurrently updated
A brief look into this:
heap_update() in T3 (called by AtCommit_Notify()) calls
HeapTupleSatisfiesUpdate(). This returns HeapTupleBeingUpdated. Once we
issue COMMIT; in T1 updates pg_listen and the tuple T3 is trying
Neil Conway writes:
On Thu, 2003-09-04 at 13:14, Kurt Roeckx wrote:
tablecmds.c: In function `validateForeignKeyConstraint':
tablecmds.c:3546: warning: dereferencing type-punned pointer will break
strict-aliasing rules
So, what should we do with this?
Rumor has it that many of
On Mon, Sep 15, 2003 at 08:09:22PM +0200, Peter Eisentraut wrote:
Neil Conway writes:
On Thu, 2003-09-04 at 13:14, Kurt Roeckx wrote:
tablecmds.c: In function `validateForeignKeyConstraint':
tablecmds.c:3546: warning: dereferencing type-punned pointer will break
strict-aliasing
I think calling it 'here-document' quoting is possibly unwise - it is
sufficiently different from here documents in shell and perl contexts to
make it confusing.
I agree. I've tried to think of a better alternative name, but without
much success.
We could call it meta-quoting, or
On Mon, Sep 15, 2003 at 08:09:22PM +0200, Peter Eisentraut wrote:
Neil Conway writes:
On Thu, 2003-09-04 at 13:14, Kurt Roeckx wrote:
tablecmds.c: In function `validateForeignKeyConstraint':
tablecmds.c:3546: warning: dereferencing type-punned pointer will break
strict-aliasing
On Mon, Sep 15, 2003 at 01:28:52AM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
#: utils/adt/acl.c:780
msgid cannot remove the world ACL
What exactly is the world ACL?
Privileges granted to PUBLIC --- the ACL code always keeps PUBLIC
privileges as an ACL entry,
Alvaro Herrera writes:
#: utils/adt/acl.c:780
msgid cannot remove the world ACL
What exactly is the world ACL? The code there is not too commented
and I couldn't find out what's this about. Some sort of default or
initial ACL maybe?
I've changed to message to aclitem for public may not
We've seen several complaints now about pg_dump failing to restore
schemas that were created by a superuser via a command like
CREATE SCHEMA joe AUTHORIZATION joe
The pg_dump script tries to do
\c - joe
CREATE SCHEMA joe
which fails if joe doesn't have privileges to create
Jeroen Ruigrok/asmodai [EMAIL PROTECTED] wrote:
-On [20030911 15:43], Tom Lane ([EMAIL PROTECTED]) wrote:
We can't ALTER a table that's already in use when the first ALTER
starts, either --- its attempt to exclusive-lock the table will fail.
But once you get the exclusive lock, you can (in
Alvaro Herrera [EMAIL PROTECTED] writes:
On Mon, Sep 15, 2003 at 01:28:52AM -0400, Tom Lane wrote:
Or rewrite entirely. Do you have a better wording?
Yes. In fact something very similar appears in regproc.c, line 636:
if (nargs == 1)
ereport(ERROR,
Gavin Sherry [EMAIL PROTECTED] writes:
A user on IRC came across the following tuple concurrently updated error
when using LISTEN/NOTIFY intensively.
I've applied a fix for this to CVS tip.
Thinking about the implications of rolling back UNLISTEN, it occurs to
me that there is another possible
On Mon, 15 Sep 2003, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
A user on IRC came across the following tuple concurrently updated error
when using LISTEN/NOTIFY intensively.
I've applied a fix for this to CVS tip.
Great.
I think that whenever we get around to rewriting
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Hm. A quick grep shows that our *only* use of gethostbyname is in
src/port/getaddrinfo.c. Seems like we should omit this porting
requirement on platforms that have getaddrinfo.
See the post I just made --- fe-secure.c calls
I get the following compiler error messages when doing a make on current CVS:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic
-I../../../../src/interfaces/ecpg/include -I../../../../src/include/utils
-I../../../../src/include -g -c timestamp.c -o timestamp.o
timestamp.c: In
Bruno Wolff III [EMAIL PROTECTED] writes:
I get the following compiler error messages when doing a make on current CVS:
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic
-I../../../../src/interfaces/ecpg/include -I../../../../src/include/utils
-I../../../../src/include -g -c
Zeugswetter Andreas SB SD [EMAIL PROTECTED] writes:
You can get around that problem by adding the SSL library to the link line
manually (-lssl).
Sorry I don't have time to fix it right now.
A minimal patch to fix this might look like the attached. But I'm not sure
it's sufficient; potentially
42 matches
Mail list logo
