Re: AllocSetStats uses fprintf instead of elog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AllocSetStats uses fprintf instead of elog
Date: 2007-11-16 16:30:13
Message-ID: 13562.1195230613@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Function AllocSetStats uses fprintf instead of standard logging method.
> Is there any reason for it?

Yes: it's typically called in zero-free-memory situations, and we don't
want to depend on elog() succeeding to be able to find out what happened.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-11-16 17:08:22 Re: [COMMITTERS] pgsql: update files for beta3
Previous Message Tom Lane 2007-11-16 16:22:23 Re: strange tuple from ExecutorRun