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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Noah Misch <noah@leadboat.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Andrey M. Borodin <x4mmm@yandex-team.ru>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Amul Sul <sulamul@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pg_amcheck contrib application
Date: Tue, 16 Mar 2021 14:52:22 -0400
Message-ID: <3388160.1615920742@sss.pgh.pa.us> (raw)
In-Reply-To: <E127C435-D276-4E2B-9A19-F52899A50BFA@enterprisedb.com>
References: <A80D68F6-E38F-482D-9522-E2FB6AAFE8A1@enterprisedb.com>
	<CA+TgmoY3_U=QuQWo4DArBSp+tg2MiCHLwDN_9U2H_iTxj3UcjA@mail.gmail.com>
	<9E76E46A-48B2-4869-BD0C-422204C1F767@enterprisedb.com>
	<F0A1FD70-A2F4-4528-8A03-8650CAEC0554@enterprisedb.com>
	<20210313184612.GA3195145@rfd.leadboat.com>
	<930621E5-5D10-456D-8CE4-CF629A6C4669@enterprisedb.com>
	<20210313191841.GB3195145@rfd.leadboat.com>
	<3012106.1615827854@sss.pgh.pa.us>
	<C2C142F3-F740-4197-B507-20B28B7395AC@enterprisedb.com>
	<3053552.1615834640@sss.pgh.pa.us>
	<20210316060913.GA3323238@rfd.leadboat.com>
	<7BCE9084-9381-471F-90F2-FAD99B7FE3DB@enterprisedb.com>
	<3254547.1615910855@sss.pgh.pa.us>
	<7CFAF7EF-4EA7-4CB6-B2C7-EC7F4512AE50@enterprisedb.com>
	<16B79A18-48F3-404D-8DC5-53528E85A7AC@enterprisedb.com>
	<CA+TgmoYFwii3cgfc-yNzEgFce=zWP08Nt56pAyffqpXjgg1UxA@mail.gmail.com>
	<3360174.1615916917@sss.pgh.pa.us>
	<E127C435-D276-4E2B-9A19-F52899A50BFA@enterprisedb.com>

Mark Dilger <mark.dilger@enterprisedb.com> writes:
> CopyStatistics seems to just copy Form_pg_statistic without regard for
> who owns the toast.  Is this safe?

No less so than a ton of other places that insert values that might've
come from on-disk storage.  heap_toast_insert_or_update() is responsible
for dealing with the problem.  These days it looks like it's actually
toast_tuple_init() that takes care of dereferencing previously-toasted
values during an INSERT.

			regards, tom lane





view thread (161+ messages)  latest in thread

Message-ID: <3388160.1615920742@sss.pgh.pa.us>
Permalink:  ../3388160.1615920742@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3388160.1615920742@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, mark.dilger@enterprisedb.com, robertmhaas@gmail.com, noah@leadboat.com, pg@bowt.ie, thomas.munro@gmail.com, x4mmm@yandex-team.ru, sfrost@snowman.net, michael@paquier.xyz, sulamul@gmail.com, dilipbalaut@gmail.com, andres@anarazel.de
  Subject: Re: pg_amcheck contrib application
  In-Reply-To: <3388160.1615920742@sss.pgh.pa.us>

* 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