Steve Wampler wrote:
Would it be (is it?) possible to add timestamp to the log
messages put out by postgresql? I've got several databases
running in an environment where users have this annoying
habit of coming up to me with ("Oh yes, three days ago around
4pm our instrument had trouble writing t
[EMAIL PROTECTED] writes:
> Is there ay way I can help with this debugging?
Can you speculate on what might have caused the crash?
Is the crash reproducible?
When the backend crashed, it should have produced a core file
(assuming your system is configured to do so). Can you post the
stacktrace y
Elliot Lee <[EMAIL PROTECTED]> writes:
> http://archives.postgresql.org/pgsql-hackers/2000-07/msg00483.php
> I'm having this same problem with postgresql 7.3.4.
You aren't having the "same" problem, because that UNION bug was fixed
ages ago.
> Easy to reproduce by running an 'INSERT' query.
Let'
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Is there anything stopping us going through the code and finding all
> ereports that can be fixed by a REINDEX, and issue a HINT with all of
> them saying that they should REINDEX the broken index?
How would you know which ones correspond to
I get the following error when vacuuming a db or inserting
a big value in a column of a toastable datatype (GEOMETRY).
ERROR: Index pg_toast_8443892_index is not a btree
My last action has been killing a psql that was getting
mad about receiving too much input and beeping as hell
(readline issue
Any chance you might be able to put together a HOWTO on this? I think it
would be extremely valuable to a lot of people.
On Tue, Nov 25, 2003 at 11:25:34PM -0500, Andrew Sullivan wrote:
> On Mon, Nov 24, 2003 at 11:08:44PM -0600, Jim C. Nasby wrote:
>
> > Has anyone looked at using replication as
Kurt Roeckx wrote:
> It seems that on_shmem_exit() first argument is a function that
> needs to be called back. The function itself doesn't have a
> prototype, but it's called with and int and Datum as argument
> when it's used.
>
> It seems that almost none of the functions it calls will actuall
It seems that on_shmem_exit() first argument is a function that
needs to be called back. The function itself doesn't have a
prototype, but it's called with and int and Datum as argument
when it's used.
It seems that almost none of the functions it calls will actually
need any argument, I could on
Tom Lane wrote:
Kurt Roeckx <[EMAIL PROTECTED]> writes:
I can compile current cvs with gcc 2.95.3, openssl 0.9.7b and
zlib 1.2.1.
"current CVS" meaning "since I fixed the include order" ?
The little code snippet I posted earlier should do to test out
compilers, if people want to.
Lookin
Jan Wieck <[EMAIL PROTECTED]> writes:
> Good question. Using my cvsup tree here, which I did sup today already.
> So what -D would trigger the failure?
Hopefully, you can't ...
If you revert src/bin/pg_dump/pg_backup_archiver.h to version 1.54
you'd see the problem, assuming your compiler is vul
Is there ay way I can help with this debugging?
On Mon, 8 Dec 2003, Tom Lane wrote:
> Date: Mon, 08 Dec 2003 14:03:42 -0500
> From: Tom Lane <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers list <[EMAIL PROTECTED]>
> Subject: Re: [HACKERS] 73.5 and uw 713
>
> [EMAIL PROTECTED] write
Tom Lane wrote:
Kurt Roeckx <[EMAIL PROTECTED]> writes:
I can compile current cvs with gcc 2.95.3, openssl 0.9.7b and
zlib 1.2.1.
"current CVS" meaning "since I fixed the include order" ?
Good question. Using my cvsup tree here, which I did sup today already.
So what -D would trigger the failure?
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> I can compile current cvs with gcc 2.95.3, openssl 0.9.7b and
> zlib 1.2.1.
"current CVS" meaning "since I fixed the include order" ?
regards, tom lane
---(end of broadcast)---
TIP 9
Kurt Roeckx wrote:
On Mon, Dec 08, 2003 at 01:27:35PM -0500, Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I've been able to reproduce this on one of my machines, and it's nasty.
> In that case I'm confused about why this code compiles on my machine:
What compile
On Mon, Dec 08, 2003 at 01:27:35PM -0500, Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> I've been able to reproduce this on one of my machines, and it's nasty.
>
> > In that case I'm confused about why this code compiles on my machine:
>
> What compiler are
[EMAIL PROTECTED] writes:
> I've upgraded my system from 7.3.4 to 7.3.5 yesterday and have already
> experienced to crash during vacuum full.
> I have'nt recompiled with debug yet but it's a sigsegv in function
> repair_frag in vacuum.c
Considering that vacuum.c hasn't changed in that branch since
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I've been able to reproduce this on one of my machines, and it's nasty.
In that case I'm confused about why this code compiles on my machine:
What compiler are you using? I'm using gcc 2.95.3 (on the
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>>> test=# select count(a.*) from pg_indexes a limit 10;
>>> server closed the connection unexpectedly
>>
>> Hmmm ... the crash is certainly UnGood, but is there any reason we
>> should accept this query rather than generating an error?
> If the SQL is not
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I've been able to reproduce this on one of my machines, and it's nasty.
> In that case I'm confused about why this code compiles on my machine:
What compiler are you using? I'm using gcc 2.95.3 (on the machine that
shows the failure
Hi all,
I've upgraded my system from 7.3.4 to 7.3.5 yesterday and have already
experienced to crash during vacuum full.
I have'nt recompiled with debug yet but it's a sigsegv in function
repair_frag in vacuum.c
Does it ring a bell?
Regards
--
Olivier PRENANT Tel: +33-5-61-50-97
tgl wrote:
> strk <[EMAIL PROTECTED]> writes:
> > gis=# reindex table pg_toast_8443892; -- this was an assuption I made
> > ERROR: Relation "pg_toast_8443892" does not exist
>
> If it's 7.3 or later you need to say
>
> reindex table pg_toast.pg_toast_8443892;
>
> regards,
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Andrew Dunstan wrote:
fresh checkout just compiled fine for me on Linux (RH8) with ssl
enabled. Maybe it is your openssl installation?
It is openssl 0.9.7c. 7.4 CVS compiles fine so I don't see how it can
be my SSL insta
Greg Stark <[EMAIL PROTECTED]> writes:
> Syntax errors in known good code, especially header files are a typical
> symptom of missing typedefs. A good thing to know to recognize right away or
> else you'll spend lots of time puzzling over seemingly good code.
Actually it turns out the error was th
strk <[EMAIL PROTECTED]> writes:
> gis=# reindex table pg_toast_8443892; -- this was an assuption I made
> ERROR: Relation "pg_toast_8443892" does not exist
If it's 7.3 or later you need to say
reindex table pg_toast.pg_toast_8443892;
regards, tom lane
-
strk wrote:
JanWieck wrote:
strk wrote:
> I get the following error when vacuuming a db or inserting
> a big value in a column of a toastable datatype (GEOMETRY).
>
> ERROR: Index pg_toast_8443892_index is not a btree
>
> My last action has been killing a psql that was getting
> mad about rec
> >> int CRYPTO_set_locked_mem_functions(void *(*m)(size_t), void (*free_func)(void
> >> *));
>
> If there's a missing typedef shouldn't we see something like this:
>
> `size_t' undeclared (first use in this function)
>
> (assuming he is using gcc)?
Try it.
typedefs are weird in the C l
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> (BTW, the INSTALL file says you can use --with-openssl=/path but
Only because it hasn't yet been rebuilt from installation.sgml.
regards, tom lane
---(end of broadcast)---
TIP 2:
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Andrew Dunstan wrote:
>> fresh checkout just compiled fine for me on Linux (RH8) with ssl
>> enabled. Maybe it is your openssl installation?
> It is openssl 0.9.7c. 7.4 CVS compiles fine so I don't see how it can
> be my SSL install.
I've been able to
JanWieck wrote:
> strk wrote:
>
> > I get the following error when vacuuming a db or inserting
> > a big value in a column of a toastable datatype (GEOMETRY).
> >
> > ERROR: Index pg_toast_8443892_index is not a btree
> >
> > My last action has been killing a psql that was getting
> > mad a
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Where is the typedef here:
int CRYPTO_set_locked_mem_functions(void *(*m)(size_t), void (*free_func)(void *));
size_t ...
If there's a missing typedef shouldn't we see something like this:
`size_t' undeclared (first use in thi
strk wrote:
I get the following error when vacuuming a db or inserting
a big value in a column of a toastable datatype (GEOMETRY).
ERROR: Index pg_toast_8443892_index is not a btree
My last action has been killing a psql that was getting
mad about receiving too much input and beeping as hell
(r
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Where is the typedef here:
> int CRYPTO_set_locked_mem_functions(void *(*m)(size_t), void (*free_func)(void *));
size_t ...
regards, tom lane
---(end of broadcast)---
TIP 8: expl
Bruce Momjian wrote:
Andrew Dunstan wrote:
fresh checkout just compiled fine for me on Linux (RH8) with ssl
enabled. Maybe it is your openssl installation?
It is openssl 0.9.7c. 7.4 CVS compiles fine so I don't see how it can
be my SSL install.
I just tried with this version of openss
Joe Conway wrote:
> > Is that something broken on my system???
>
> Bruce just reported something like this too. I had a somewhat similar
> issue about a week and a half ago. It may be a long shot, but try:
>
> ./configure \
> --with-openssl \
> --with-krb5 \
> --with-includes=/usr/kerberos
Andrew Dunstan wrote:
>
> fresh checkout just compiled fine for me on Linux (RH8) with ssl
> enabled. Maybe it is your openssl installation?
It is openssl 0.9.7c. 7.4 CVS compiles fine so I don't see how it can
be my SSL install.
--
Bruce Momjian| http://candle.pha.
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Attached is a compile failure I am seeing in CVS HEAD in bin/pg_dump.
>
> Hmm. I made some what-I-thought-were-unimportant changes in the order
> of header inclusions in pg_dump. Probably what you are seeing is a
> previously unnoti
At 2003-12-07 18:19:26 +0100, [EMAIL PROTECTED] wrote:
>
> There is a new type in C99 for "integer that can hold a pointer
> value". I think it's called intptr_t resp. uintptr_t, but I don't have
> the standard around.
Yes, they're called intptr_t and uintptr_t (ยง7.18.1.4), but they're both
option
I get the following error when vacuuming a db or inserting
a big value in a column of a toastable datatype (GEOMETRY).
ERROR: Index pg_toast_8443892_index is not a btree
My last action has been killing a psql that was getting
mad about receiving too much input and beeping as hell
(readli
38 matches
Mail list logo
