| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | trivial patch for dynahash logging |
| Date: | 2014-09-27 21:43:51 |
| Message-ID: | CAMkU=1xAr8GOmRtkpWkGtWkR=cnDj9KtQPP5-5sFt4wz2fdEAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
under HASH_STATISTICS, the output reporting "this HTAB" upon destruction is
pretty useless. Which HTAB would this one be? It is not necessarily the
most recently created one.
This makes it output the %p to the actual HTAB, so it can be matched up
with the logging of the creation.
I'm not sure why it bypasses elog. Is that so it can run during start-up
before elog is active? I'd like to make it go through elog so that
log_line_prefix are applied, but then it would no longer be a trivial patch.
Cheers,
Jeff
| Attachment | Content-Type | Size |
|---|---|---|
| dynahash.patch | text/x-patch | 959 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-09-27 22:09:05 | Re: trivial patch for dynahash logging |
| Previous Message | Marko Tiikkaja | 2014-09-27 20:50:42 | Re: pgcrypto: PGP armor headers |