On Mon, 27 Aug 2001, Tom Lane wrote:
> The latter is what I'm interested in, since \d doesn't invoke anything
> that I'd consider crash-prone. Could you submit a debugger backtrace
> from the crash?
I should do that. But, since it's the back-end that's crashing, I'd need
to find some way of getting a core dump. So far, it isn't producing any.
I'll have to play with the environment to see why.
> Yes, I know, 6.* was not very careful about defending itself from tuples
> over 8K. But 7.0 is, which is why I don't think that the tuple length
> is relevant. I'd like to quit bandying accusations about and instead
> find out *exactly why* Postgres is crashing on you, so that we can
> either fix it or confirm that it's been fixed already.
Yeah, I know. I was just trying to defend mysql. ^_^ We use both, and so
far, it's been the smaller headache, so... I'll do what I can to get you
a backtrace. The really strange thing is, one of our newwer databases has
started hanging on vacuums. That's a 7.1.1, so the 8k thing shouldn't be
any kind of issue in the slightest thanks to the new internal structures.
But something is corrupt enough to break vaccum badly. That doesn't make
me feel very good. The worst part is, while it's hung on the vacuum, idle
connections just start piling up until we have to restart the DB.
That's no good.
--
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Shaun M. Thomas INN Database Programmer |
| Phone: (309) 743-0812 Fax : (309) 743-0830 |
| Email: [EMAIL PROTECTED] AIM : trifthen |
| Web : hamster.lee.net |
| |
| "Most of our lives are about proving something, either to |
| ourselves or to someone else." |
| -- Anonymous |
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
