Tom Lane wrote:
>
> Adriaan Joubert <[EMAIL PROTECTED]> writes:
> > Yes, dropping the CPP flags solves the problem for us. I assume all
> > platforms have long long now?
>
> Surely you jest.
Yep, it was a rhetorical question.
I think we probably do need the CPP defines from my patch in there,
Adriaan Joubert <[EMAIL PROTECTED]> writes:
> Yes, dropping the CPP flags solves the problem for us. I assume all
> platforms have long long now?
Surely you jest.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you c
> Could you please try to just remove the cpp flag? Also I wonder why you are
> using "long long int" instead of just "long int" in your C program. Well
> that is the people who complained to you.
Yes, dropping the CPP flags solves the problem for us. I assume all
platforms have long long now?
W
> Well, bad news. After a few more tries to crash the backend, the whole
> postmaster crashed and didn't rise back.
> It fails to start up reporting "Apr 4 18:53:05 wale
> postgres[71618]: [9]
> FATAL 2: XLogWrite: write request is past end of log" to syslog.
Ok, this one is easy to fix. From
Ciaran Johnston <[EMAIL PROTECTED]> writes:
> Sorry to bother you's but I am currently doing a database comparison and
> have been trying to get postgresql installed. I'm running Solaris 2.7. I
> downloaded pgsql 7.03 and ran ./configure in the src/ directory. This
> was fine until the very end wh
At 5:47 PM -0500 4/4/01, Neil Tiffin wrote:
>Using current cvs version on Mac OS X 10.0
>
>test horology ... FAILED
I can't reproduce this on a 10.0 (4K78) system. I just ran the regression tests from
cvs HEAD downloaded @ 16:10 PDT on a G3/350. It also passed several dozen iteratio
On Wed, Apr 04, 2001 at 06:46:12PM +0300, Martín Marqués allegedly wrote:
> Why are you running configure inside src/? I'm not sure if the 7.0.x had the
> configure on the src/ dir or the root.
It's in the src dir with 7.0.x alright.
> You could take a look at 7.1RC[2-3], which looks pretty sta
On Thursday 05 April 2001 00:41, Thomas Lockhart wrote:
> I've got patches for the regression tests to work around the "time with
> time zone" DST problem. Will apply to the tree asap, and will post a
> message when that is done.
Is RC3 going out or should I think about RC2?
Saludos... ;-)
--
On Wed, Apr 04, 2001 at 10:56:27AM -0400, Tom Lane allegedly wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > On Wed, 4 Apr 2001, Tom Lane wrote:
> >> I think we've got to remove that failing horology test before we wrap RC3.
>
> > can we comment out the test for now, so that its still
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Anyone have suggestions for Mathew?
>> for postgresql-7.1RC2.tar.gz, here is my `make check' for NetBSD/sparc64:
>> digging into the regression.diffs, i can see that:
>> - reltime failed because it just had:
>> ! psql: Backend startup failed
The pos
On Wed, 4 Apr 2001, Thomas Lockhart wrote:
> I've got patches for the regression tests to work around the "time with
> time zone" DST problem. Will apply to the tree asap, and will post a
> message when that is done.
Sounds cool ... I'll scheduale an RC3 then, around that bug being fixed
...
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On Wed, 4 Apr 2001, Mikheev, Vadim wrote:
> Everything has been quiet, as far as patches are concerned,
> for the past 24+hrs ... I'd like to roll (and actually announce)
> an solid RC3 tonight, with announce first thing tomorrow morning,
> unless an
> Well, bad news. After a few more tries to crash the backend, the whole
> postmaster crashed and didn't rise back.
> It fails to start up reporting "Apr 4 18:53:05 wale
> postgres[71618]: [9]
> FATAL 2: XLogWrite: write request is past end of log" to syslog.
Hmmm, the only XLogWrite startup p
Using current cvs version on Mac OS X 10.0 built with
./configure
make
made check
test horology ... FAILED
from the regression.diffs file
Is this a problem or not?
Neil Tiffin
Chicago
[localhost:src/test/regress] ntiffin% cat regression.diffs
*** ./expected/horology.out Sun
I've got patches for the regression tests to work around the "time with
time zone" DST problem. Will apply to the tree asap, and will post a
message when that is done.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked
KS <[EMAIL PROTECTED]> writes:
> Well, bad news. After a few more tries to crash the backend, the whole
> postmaster crashed and didn't rise back.
> It fails to start up reporting "Apr 4 18:53:05 wale postgres[71618]: [9]
> FATAL 2: XLogWrite: write request is past end of log" to syslog.
Ugh.
On Wednesday 04 April 2001 22:42, Ciaran Johnston wrote:
> Hi,
>
> Sorry to bother you's but I am currently doing a database comparison and
> have been trying to get postgresql installed. I'm running Solaris 2.7. I
> downloaded pgsql 7.03 and ran ./configure in the src/ directory. This
> was fine
On Wednesday 04 April 2001 13:29, Pete Forman wrote:
> > Solaris 2.7-8 Sparc7.1 2001-03-22, Marc Fournier
>
> I've reported Solaris 2.6 Sparc as working on a post-RC1 snapshot.
Same for Solaris 8 Sparc, but only tested with RC1.
--
El mejor sistema operativo es aquel que te da de comer.
Cu
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Two changes for the TODO list.
>>
>> 1. Under "RELIABILITY/MISC", add:
>>
>> Write out a CRC with each data block, and verify it on reading.
>>
>> 2. Under SOURCE CODE, I believe Tom has already implemented:
>>
>> Correct CRC WAL code to be a real C
> > TODO updated. I know we did number 2, but did we agree on #1 and is it
> > done?
>
> #2 is indeed done. #1 is not done, and possibly not agreed to ---
> I think Vadim had doubts about its usefulness, though personally I'd
> like to see it.
That was my recollection too. This was the discus
>
> Bruce,
>
> Two changes for the TODO list.
>
> 1. Under "RELIABILITY/MISC", add:
>
> Write out a CRC with each data block, and verify it on reading.
>
> 2. Under SOURCE CODE, I believe Tom has already implemented:
>
> Correct CRC WAL code to be a real CRC64 algorithm
TODO updated.
Hi,
Sorry to bother you's but I am currently doing a database comparison and
have been trying to get postgresql installed. I'm running Solaris 2.7. I
downloaded pgsql 7.03 and ran ./configure in the src/ directory. This
was fine until the very end when this error appeared:
creating ./config.stat
On Wed, Apr 04, 2001 at 05:47:50PM +0300, Adriaan Joubert wrote:
> This has nothing to do with the backend. ecpg itself core-dumps after
> calling abort() at the end of the switch statement in typename.c, when
> processing a .pgc file. As people complained to me about ecpg
Yes, I did understand t
I am trying to build Mac OSX 10.0 from the current cvs.
./configure --with-perl --with-openssl --enable-syslog |& tee configure.logfile
make |& tee Makefile.logfile
Running Mkbootstrap for plperl ()
chmod 644 plperl.bs
LD_RUN_PATH="" cc -o blib/arch/auto/plperl/plperl.bundle -bundle
-unde
(cc'd the -hackers mailing list)
Thanks for the reports Matthew. There is a single failure in the
NetBSD/sparc64 test due to a problem in the reltime test (or in starting
the reltime test). There is a different failure in your NetBSD/sparc
test, but since you are not confident about your installa
On Wed, 4 Apr 2001, Mikheev, Vadim wrote:
> > Everything has been quiet, as far as patches are concerned,
> > for the past 24+hrs ... I'd like to roll (and actually announce)
> > an solid RC3 tonight, with announce first thing tomorrow morning,
> > unless anyone has anythign they aer sitting on?
> Everything has been quiet, as far as patches are concerned,
> for the past 24+hrs ... I'd like to roll (and actually announce)
> an solid RC3 tonight, with announce first thing tomorrow morning,
> unless anyone has anythign they aer sitting on?
We still have opened report about losing files af
Hi,
I have a string that is getting encoded using blowfish in postgres
(using my own function written in C for PG) and storted in the
database.
The problem is, that with some strings after encoding is done, I end up
with a special character in the middle of the encoded string that is
in
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On Wed, 4 Apr 2001, Tom Lane wrote:
>> I think we've got to remove that failing horology test before we wrap RC3.
> can we comment out the test for now, so that its still in there, but not
> tested? or is there absolutely non way that we can fix th
Michael Meskes wrote:
>
> On Wed, Apr 04, 2001 at 03:35:34PM +0300, Adriaan Joubert wrote:
> > OK, I see. Problem is that without the fix ecpg aborts when writing to a
> > table with an int8 column using valid code.
>
> Sorry, I still don't seem to understand that. Data between ecpg and the
> ba
On Wed, 4 Apr 2001, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > Everything has been quiet, as far as patches are concerned, for the past
> > 24+hrs ... I'd like to roll (and actually announce) an solid RC3 tonight,
> > with announce first thing tomorrow morning, unless any
> You could ask. Just to ignore reports that you have asked for is not
> polite. My report was based on a virgin, unpatched 2.4.2 kernel, and
> (as noted) the Debian-packaged glibc-2.2.2.
The simple fact is that the vast majority of Linux boxes are not yet
running 2.4 kernels, so imho it is not
Michael Meskes <[EMAIL PROTECTED]> writes:
>> all exist on alpha and are all 64 bits, but HAVE_LONG_LONG_INT_64 is not
>> defined, so ecpg cannot handle ECPGt_long_long types. It is not clear to
> I see. I was under the impression that HAVE_LONG_LONG_INT_64 should be
> defined if long long int is
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> Everything has been quiet, as far as patches are concerned, for the past
> 24+hrs ... I'd like to roll (and actually announce) an solid RC3 tonight,
> with announce first thing tomorrow morning, unless anyone has anythign
> they aer sitting on?
I th
There is an ELOG_TIMESTAMPS options and some others in include/config.h or
include/config.h.in. I think that is where you get the pid of the
backend and stuff. I agree it needs more detail, at least the process
id.
[ Charset ISO-8859-1 unsupported, converting... ]
> I just have to setup a tron
On Wed, Apr 04, 2001 at 03:35:34PM +0300, Adriaan Joubert wrote:
> OK, I see. Problem is that without the fix ecpg aborts when writing to a
> table with an int8 column using valid code.
Sorry, I still don't seem to understand that. Data between ecpg and the
backend is tranfered in ascii only. Wha
I just have to setup a trong logging of users postgres activity using php
script.
It's work well and my disk is going full quickly.
i have a file like this
{ TARGETENTRY
:resdom
{ RESDOM
:resno 2
:restype 1043
:restypmod 24
:re
On Wed, Apr 04, 2001 at 11:26:01AM +0200, Konstantinos Agouros wrote:
> Hi,
>
> I just tried to go to RC2 on Solaris 7. However the configure fails at the opt-
> reset-test because the linker can not find the library to resolve it.
> The configureline was:
> ./configure --with-perl --with-openssl
I packaged up an RC2 over the weekend, and pretty much as soon as I had it
packaged and in place, before I could announce it, there were several
patches thrown in ... so, I left it there, let anyone who happened to see
it pick it up, but didn't announce it ...
Everything has been quiet, as far a
On Tue, Apr 03, 2001 at 06:32:25PM +0300, Adriaan Joubert wrote:
> we had a problem on Alpha that in interfaces/ecpg/lib/typename.c we
> have
> HAVE_LONG_INT_64 defined, but not HAVE_LONG_LONG_INT_64. Consequently no
Sure since that means your long int and not your long long int is 64 bits.
On Tue, 3 Apr 2001, Nathan Myers wrote:
> On Tue, Apr 03, 2001 at 11:19:04PM +, Thomas Lockhart wrote:
> > > I saw three separate reports of successful builds on Linux 2.4.2 on x86
> > > (including mine), but it isn't listed here.
> >
> > It is listed in the comments in the real docs. At leas
> Solaris 2.7-8 Sparc7.1 2001-03-22, Marc Fournier
I've reported Solaris 2.6 Sparc as working on a post-RC1 snapshot.
--
Pete Forman -./\.- Disclaimer: This post is originated
WesternGeco -./\.- by myself and does not represent
[EMAIL PROTECTED] -./\.-
Hi,
I just tried to go to RC2 on Solaris 7. However the configure fails at the opt-
reset-test because the linker can not find the library to resolve it.
The configureline was:
./configure --with-perl --with-openssl=/usr/local/ssl --enable-odbc --with-CXX
--enable-locale
Could someone give me a
>
>Here are the up-to-date platforms:
>
>AIX 4.3.3 RS6000 7.1 2001-03-21, Gilles Darold
>BeOS 5.0.4 x86 7.1 2000-12-18, Cyril Velter
I just checked RC2 on BeOS and everything is OK except the Horlogy test
(regarding previous discussions, it seems to be normal ?)
cyril
select ve
44 matches
Mail list logo
