| From: | nicolas paris <nicolas(dot)paris(at)riseup(dot)net> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Merge David and Goliath tables efficiently |
| Date: | 2023-06-19 12:09:37 |
| Message-ID: | e938f93dded1dd0ffe220946a303215991a36bd6.camel@riseup.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2023-06-19 at 13:34 +0200, Tomas Vondra wrote:
>
>
> On 6/18/23 22:57, nicolas paris wrote:
> > > ...
> > > Well, I kinda doubt you have 17023331531230 rows (not even
> > > physically
> > > possible with 2TB disk), so that's immediately suspicious.
> >
> > Below is the full plan for the strategy 2.1 (Indeed the previous
> > email
> > plan was truncated and wrong, sorry for that).
> >
>
> None of the plans has estimates anywhere close to 17023331531230, so
> where did that come from?
>
Well this was an old plan where there was an issue: the david table did
not have the same partitioning scheme as goliath. It was partitioned by
an other column.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | nicolas paris | 2023-06-19 12:20:26 | Re: Merge David and Goliath tables efficiently |
| Previous Message | Tomas Vondra | 2023-06-19 11:53:50 | Re: Merge David and Goliath tables efficiently |