| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gunther <raj(at)gusw(dot)net>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Out of Memory errors are frustrating as heck! |
| Date: | 2019-04-22 17:15:10 |
| Message-ID: | CAMkU=1yeD4n71B2nwTn==aeMz+e7uHVT6QWoaiDA15++h70Lvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, Apr 20, 2019 at 4:48 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Gunther <raj(at)gusw(dot)net> writes:
> > and checked my log file and there was nothing before the call
> > MemoryContextStats(TopPortalContext) so I don't understand where this
> > printf stuff is ending up.
>
> It's going to stdout, which is likely block-buffered whereas stderr
> is line-buffered, so data from the latter will show up in your log
> file much sooner. You might consider adding something to startup
> to switch stdout to line buffering.
>
Is there a reason to not just elog the HJDEBUG stuff? With some of the
other DEBUG defines, we will probably be using them before the logging
system is set up, but surely we won't be doing Hash Joins that early?
I think we could just get rid of the conditional compilation and elog this
at DEBUG1 or DEBUG2. Or keep the conditional compilation and elog it at
LOG.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-22 17:57:34 | Re: Out of Memory errors are frustrating as heck! |
| Previous Message | Tomas Vondra | 2019-04-22 13:04:15 | Re: Out of Memory errors are frustrating as heck! |