pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: pinker <pinker@onet.eu>
To: pgsql-bugs@postgresql.org
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Date: Sun, 18 Oct 2020 13:49:01 -0700 (MST)
Message-ID: <1603054141539-0.post@n3.nabble.com> (raw)
In-Reply-To: <1603052486329-0.post@n3.nabble.com>
References: <1603050466566-0.post@n3.nabble.com>
	<1603050580276-0.post@n3.nabble.com>
	<235509.1603051243@sss.pgh.pa.us>
	<1603051414438-0.post@n3.nabble.com>
	<236292.1603052323@sss.pgh.pa.us>
	<1603052486329-0.post@n3.nabble.com>

ok, it sounds so crazy that i cannot believe...
it crashes when value in column relname is 'promotion' also with
'promotion_[something]' it does not crash when other strings are used.... !!

COPY public.stat_user_tables (now, relid, schemaname, relname, seq_scan,
seq_tup_read, idx_scan, idx_tup_fetch, n_tup_ins, n_tup_upd, n_tup_del,
n_tup_hot_upd, n_live_tup, n_dead_tup, n_mod_since_analyze, last_vacuum,
last_autovacuum, last_analyze, last_autoanalyze, vacuum_count,
autovacuum_count, analyze_count, autoanalyze_count) FROM stdin;
2020-10-17 01:35:01.935309+02	16802	public	promotion	311	7775	0	0	0	0	00	25
0	0	\N	2020-10-07 09:08:41.061339+02	2020-10-16 04:47:58.421258+02	\N	01	1	0
2020-10-17 01:35:01.935309+02	123040	public	promotion	2	0	1	0	0	0	00	0	0	0
\N	2020-10-07 09:08:41.264478+02	2020-10-16 04:47:31.591375+02	\N	01	1	0
\.

COPY public.table_sizes (now, oid, table_schema, table_name, row_estimate,
total_bytes, index_bytes, toast_bytes, table_bytes, total, index, toast,
"table") FROM stdin;
2020-10-16 18:13:57.089157+02	123045	public	promotion	1910	23142400	5496832
139264	1750630422 MB	5368 kB	136 kB	17 MB
2020-10-16 18:13:57.089157+02	16802	public	promotion	25	57344	16384	\N	40960
56 kB	16 kB	\N	40 kB
\.




--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html





view thread (17+ messages)  latest in thread

Message-ID: <1603054141539-0.post@n3.nabble.com>
Permalink:  ../1603054141539-0.post@n3.nabble.com/
Also on:    postgresql.org/message-id/1603054141539-0.post@n3.nabble.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-bugs@postgresql.org
  Cc: pinker@onet.eu
  Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
  In-Reply-To: <1603054141539-0.post@n3.nabble.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