| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | ben m <ropeladder(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14843: CREATE TABLE churns through all memory, crashes db |
| Date: | 2017-10-06 01:32:45 |
| Message-ID: | CAB7nPqRYF76_HxdHnM8vMxBBF_XpWa86U=pBnPCJS1k_SYd8Rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 6, 2017 at 10:09 AM, ben m <ropeladder(at)gmail(dot)com> wrote:
> Thanks, I'm assuming that's the same error as I'm getting. (Where do you get
> the memory dump logs from exactly? It just took me 45 minutes to find the
> main postgres logs...)
(Please avoid top-posting)
Well, this depends on your installation and distribution, which is
decided by how Postgres is packaged and deployed on Linux Mint. The
logs are found depending on the configuration of postgresql.conf. If
you are using stderr, or csvlog as log_destination, you would find the
new function called pg_current_logfile() interesting to know what is
the current log file in use. If log_directory is defined as an
absolute path you could also directly getting to it. But this really
depends on Mint, and this is an unknown territory for me.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-06 03:57:59 | Re: BUG #14843: CREATE TABLE churns through all memory, crashes db |
| Previous Message | Tom Lane | 2017-10-06 01:16:26 | Re: pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql |