It is hard to figure out,but I inspect the source code,told me:
http://ftp.openbsd.org/pub/OpenBSD/4.9/sys.tar.gz:/usr.bin/m4/PSD.doc/m4.ms:
Line35: m4.ms 6.3 (Berkeley) 6/5/93
On Wed, Oct 19, 2011 at 05:12, Tom Lane wrote:
> Robert Young writes:
>> I've update my m4 to version 1.4.13
>> from:
So,I think it'd better to check the m4 compatiblity in ./configure
On Wed, Oct 19, 2011 at 05:10, Robert Young wrote:
> Perfect!
> I've update my m4 to version 1.4.13
> from:
> http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz
> the problem solved perfectly!
> Thank You !!!
>
-
Robert Young writes:
> I've update my m4 to version 1.4.13
> from:
> http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz
> the problem solved perfectly!
Just for the archives' sake, can you confirm which m4 version you had
before?
regards, tom lane
--
Se
Perfect!
I've update my m4 to version 1.4.13
from:
http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz
the problem solved perfectly!
Thank You !!!
# /usr/bin/gm4 --version
m4 (GNU M4) 1.4.13
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or late
I wrote:
> A little bit of googling suggests that this is a bug or incompatibility
> with openbsd's m4 (a tool that bison relies on):
> http://comments.gmane.org/gmane.comp.parsers.bison.bugs/2708
Scratch that: closer reading of the page says that the complainant was not
using some openbsd-specifi
Robert Young writes:
> On Tue, Oct 18, 2011 at 18:22, Tom Lane wrote:
>> Hmm, what version of bison are you using?
> # /usr/bin/bison -V
> bison (GNU Bison) 2.3
> Written by Robert Corbett and Richard Stallman.
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the
# /usr/bin/bison -V
bison (GNU Bison) 2.3
Written by Robert Corbett and Richard Stallman.
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
#
From:
Robert Young writes:
> Platform:
> OpenBSD 4.9 GENERIC.MP#819 amd64 Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
Hmm, what version of bison are you using? Because the ones I've dealt
with emit
typedef union YYSTYPE {
...
} YYSTYPE;
which makes the code correct as-is. Your proposed patch seem
Susanne Ebrecht writes:
> On 17.10.2011 16:41, Andreas Pflug wrote:
>> This is a little bit annoying on migration topics.
>> While not move on to a cleaner approach during the migration and use a
>> "boolean not null"?
>> Sounds much too straight forward, not mysql-ish artistic enough...
> Depend
"Vishnu S." wrote:
> I have created index on some of the tables in the custom
> tablespace. But the indexes resides in the default tablspace. Is
> there any issue in it?
No.
> Is there any chance for deleting the tablespace, if the crash
> recovery using WAL and fsync is failed?
I don't kn
good idea. I will try.
Thank you.
[]Laerson Keler
laerson.ke...@lkmc.com.br
Cel: 11 9914-4030
Res: 11 3404-4632
2011/10/17 Jaime Casanova
> On Mon, Oct 17, 2011 at 2:43 PM, Tom Lane wrote:
> >
> > There really is not any way to generate guaranteed-hole-free sequences
> > using sequence object
I changed the logic of the trigger, I'm using before and taking the next_val
().
Thank you.
[]Laerson Keler
laerson.ke...@lkmc.com.br
Cel: 11 9914-4030
Res: 11 3404-4632
2011/10/17 Tom Lane
> Laerson keler writes:
> > 2011/10/17 Tom Lane
> >> "Laerson Keler" writes:
> >> Why did you do that
Hi,
I have created index on some of the tables in the custom tablespace. But
the indexes resides in the default tablspace. Is there any issue in it?
Is there any chances for failing the crash recovery? Is there any chance
for deleting the tablespace, if the crash recovery using WAL and fsync
is fa
[Please reply to the list]
On Oct 18, 2011, at 10:45 AM, Ric Eittreim wrote:
> Hello Sachin - I have tried that and appreciate the suggestion - just did
> not work. When I did the install, I remember twice it asked for a name,
> both times I gave the same one (4 characters) - so now I'm wondering
On 17.10.2011 16:41, Andreas Pflug wrote:
Am 17.10.11 10:53, schrieb Thomas Kellerer:
Susanne Ebrecht, 17.10.2011 09:31:
Hello,
I couldn't find that somebody already mentioned it.
PostgreSQL isn't supporting CHAR(0).
An empty string has a length of 0.
CHAR(0) can have two values: NULL and e
Platform:
OpenBSD 4.9 GENERIC.MP#819 amd64 Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
Error:
gmake[4]: Entering directory `/tmp/pgxc/git/src/pl/plpgsql/src'
/usr/bin/bison -d -o pl_gram.c gram.y
gcc -DPGXC -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -Wformat
16 matches
Mail list logo
