pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pg11.1: dsa_area could not attach to segment
Date: Thu, 7 Feb 2019 09:08:32 -0600
Message-ID: <20190207150832.GL29720@telsasoft.com> (raw)
In-Reply-To: <20190207014719.GJ29720@telsasoft.com>
References: <CAEepm=2xCxHvvnqjeuD3kedH83PSaEinB0B26HBpRYMiTY5CWg@mail.gmail.com>
	<20190206062427.GX29720@telsasoft.com>
	<CAEepm=0tp5985uxOpaJeoZU6Re7h4XaaEf+5gX1Zy9TzEMAq6g@mail.gmail.com>
	<20190206063548.GZ29720@telsasoft.com>
	<CAEepm=3rCe5L6ABWi74ZcJ_zz+n8nF3AyJZpMN=bhg+U0=W46Q@mail.gmail.com>
	<20190206070819.GA29720@telsasoft.com>
	<CAEepm=3Aq=R=3f8xtH1ipBeMFvrCXk6yobWN7B__ftfkWhxrAw@mail.gmail.com>
	<20190206071940.GB29720@telsasoft.com>
	<CAEepm=18oK3LCKnPbMQeYumFVM=ZPA_v_RmsVBaP1eeF6LOB7Q@mail.gmail.com>
	<20190207014719.GJ29720@telsasoft.com>

On Wed, Feb 06, 2019 at 07:47:19PM -0600, Justin Pryzby wrote:
> FYI, I wasn't yet able to make this work yet.
> (gdb) print *segment_map->header
> Cannot access memory at address 0x7f347e554000

I'm still not able to make this work.  Actually this doesn't work even:

(gdb) print *segment_map
Cannot access memory at address 0x4227dcdd0

Thomas thought it's due to coredump_filter, but 0xff doesn't work (actually
0x7f seems to be the max here).  Any other ideas?  The core is not being
truncated, since this is on a "toy" instance with 128MB buffers.

-rw-r-----. 1 pryzbyj root 279M Feb  7 09:52 coredump

[pryzbyj@telsasoft-db postgresql]$ ~/src/postgresql.bin/bin/pg_ctl -c start -D /var/lib/pgsql/test -o '-c operator_precedence_warning=on -c maintenance_work_mem=1GB -c max_wal_size=16GB -c full_page_writes=off -c autovacuum=off -c fsync=off -c port=5678 -c unix_socket_directories=/tmp'                                                                                              waiting for server to start....2019-02-07 09:25:45.745 EST [30741] LOG:  listening on IPv6 address "::1", port 5678                                                                           2019-02-07 09:25:45.745 EST [30741] LOG:  listening on IPv4 address "127.0.0.1", port 5678                                                                                                    2019-02-07 09:25:45.746 EST [30741] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5678"
.2019-02-07 09:25:46.798 EST [30741] LOG:  redirecting log output to logging collector process
2019-02-07 09:25:46.798 EST [30741] HINT:  Future log output will appear in directory "log".
 done
server started

[pryzbyj@telsasoft-db postgresql]$ echo 0xff |sudo tee /proc/30741/coredump_filter

Justin




view thread (32+ messages)  latest in thread

Message-ID: <20190207150832.GL29720@telsasoft.com>
Permalink:  ../20190207150832.GL29720@telsasoft.com/
Also on:    postgresql.org/message-id/20190207150832.GL29720@telsasoft.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, thomas.munro@enterprisedb.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: pg11.1: dsa_area could not attach to segment
  In-Reply-To: <20190207150832.GL29720@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox