Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qQv2C-001Q6k-AT for pgsql-admin@arkaria.postgresql.org; Tue, 01 Aug 2023 19:27:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qQv29-009nsA-OZ for pgsql-admin@arkaria.postgresql.org; Tue, 01 Aug 2023 19:27:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qQv29-009ns1-Da for pgsql-admin@lists.postgresql.org; Tue, 01 Aug 2023 19:27:54 +0000 Received: from mail-oi1-x22e.google.com ([2607:f8b0:4864:20::22e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qQv28-000GEk-DL for pgsql-admin@lists.postgresql.org; Tue, 01 Aug 2023 19:27:53 +0000 Received: by mail-oi1-x22e.google.com with SMTP id 5614622812f47-3a7246ba446so117709b6e.0 for ; Tue, 01 Aug 2023 12:27:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690918071; x=1691522871; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/SZdLn6fCZDRhRURNiDKHENJ1cGU57NEGRCElmMJ634=; b=LpI5uni36Ex1vyjfhDJ82cM8/WH+XrFpimwVwkv4sfwx0YvEaqZP+0YYzRXTQ0DBl5 jMdf5Bb04xkopyVGPwisLMGvlC10CgcNvAhsmUDZhHv1QUYRX0P7aAlm8mxQbngg3tl1 eqvyZ49ANz7piTGVqHU3owVPTxX62JVRDUa1w24H/Rli0TBQU/kSXsF3QiYwPCXZ0l1C X2w+fRHB3wAV1t84xA6emE0u9uz5+KHP/Os+n5ZkBxeUrhMWsV6aVaS3Pg0KNvPu/yJE 6UHAMUAWKVB8V5aJjwwy9p19FmRuiMEisoz+M0BXGDOtcUNOonEK9bCREZr396GG/Blx Wghw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690918071; x=1691522871; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/SZdLn6fCZDRhRURNiDKHENJ1cGU57NEGRCElmMJ634=; b=iwE4bl3yD9S45aBNToWNJvQzzYeg3h+RleSUfCTFQUVzIPzJFF7xSWaYrb9uKqEeIS gPtV7q2IiLl926qo5xS2otfAWxhj4hrHVGPeb7tkH8GdPdTbieC85Wi9Hr97Tj/qC4Lo EPCTuveUw9TrnWdY5suct1zYOTOk6Tk8A9YP4Hti1vs5khBZhx2q3Uge8jqs/YpaR4mU olLLGc0Pf0fVDgAO5UTMp5A9g8HJhhRNWCAJdKexRfiVB7YpkLcQA4b8rrzrJtT/RzA4 hj0cPDPIEoN5IgY4lrU8QXIqAGl4qmYZm4i9CryxPE0IbcAR9+q/JLv1p5h8N+ME5Ep5 CrbA== X-Gm-Message-State: ABy/qLaWPdxF1wdmVUgJ49mQUiWM+wz2ZPixYn6mCU4ysQ6IkDf179Wj bLsvRZXNjSPC7e3eGuLtLBLHIz0uxHZgAwZ1TMk= X-Google-Smtp-Source: APBJJlENaGOONKBHamU+CfqNBkeuXFmUoxGcvly4vuox1jjuZLKdpAbStOor5E+bJ0LRDaSvHZANnOqEaa233g+fQN0= X-Received: by 2002:a4a:91dd:0:b0:56c:8f35:7ed2 with SMTP id e29-20020a4a91dd000000b0056c8f357ed2mr7687559ooh.0.1690918071628; Tue, 01 Aug 2023 12:27:51 -0700 (PDT) MIME-Version: 1.0 References: <155c25b62f6eab032138b93831ca4fe95158e059.camel@cybertec.at> In-Reply-To: <155c25b62f6eab032138b93831ca4fe95158e059.camel@cybertec.at> From: richard coleman Date: Tue, 1 Aug 2023 15:27:40 -0400 Message-ID: Subject: Re: analyze foreign tables To: Laurenz Albe Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000000f9230601e18b2a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000000f9230601e18b2a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Laurenz, Since my ability to program in C is basically non-existent, there's no danger of me writing custom PostgreSQL C code anytime soon. Maybe someday when I retire I'll take up C coding to keep my mind nimble. So increasing parallelization it is. Thanks again, rik. On Tue, Aug 1, 2023 at 3:15=E2=80=AFPM Laurenz Albe wrote: > On Tue, 2023-08-01 at 12:36 -0400, richard coleman wrote: > > Would it be possible to transfer table statistics between the same > version > > of PostgreSQL, ex: source is pg15, target is pg15? > > There is no support for that. > > If you know what you are doing, you might be able to mess with the catalo= g > tables, > but you would probably need server C code for that, since you cannot > normally > write to an "anyarray". > > I wouldn't recommend to go that way. > > > Otherwise, anything that can be done to speed this up would be very > helpful. > > Run the ANALYZE in many parallel sessions. I cannot think of anything > smarter. > > Yours, > Laurenz Albe > --00000000000000f9230601e18b2a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Laurenz,=C2=A0

Since my ability to prog= ram in C is basically non-existent, there's no danger of me writing cus= tom PostgreSQL C code anytime soon.=C2=A0=C2=A0

Ma= ybe someday when I retire I'll take up C coding to keep my mind nimble.=

So increasing parallelization it is.
Thanks again,=C2=A0
rik.

<= br>
On Tue,= Aug 1, 2023 at 3:15=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2023-08-01 at 12:36 -0400= , richard coleman wrote:
> Would it be possible to transfer table statistics between the same ver= sion
> of PostgreSQL, ex: source is pg15, target is pg15?

There is no support for that.

If you know what you are doing, you might be able to mess with the catalog = tables,
but you would probably need server C code for that, since you cannot normal= ly
write to an "anyarray".

I wouldn't recommend to go that way.

> Otherwise, anything that can be done to speed this up would be very he= lpful.

Run the ANALYZE in many parallel sessions.=C2=A0 I cannot think of anything= smarter.

Yours,
Laurenz Albe
--00000000000000f9230601e18b2a--