Re: row estimate for partial index

On Mon, Jan 16, 2023 at 09:59:38AM -0500, Tom Lane wrote: > Harmen writes: > > On Sat, Jan 14, 2023 at 11:23:07AM -0500, Tom Lane wrote: > >> If you are running a reasonably recent PG version you should be able to > >> fix that by setting up "extended sta

Re: row estimate for partial index

On Sat, Jan 14, 2023 at 11:23:07AM -0500, Tom Lane wrote: > Harmen writes: > > Works well enough. However, we now have an org_id which has > 10% of the > > rows, > > but only a handful rows where "deleted is null" matches (so the org has a > > lot > &g

row estimate for partial index

n org8448 (cost=0.00..4.13 rows=1256006 width=0) (actual time=0.841..0.841 rows=7 loops=1) Is this expected? Is there a way to improve this? Thanks! Harmen

Re: delete statement returning too many results

options: either the query is broken, or postgres is broken. Assuming it's the former, would there be a way to make it clearer that the "obvious" (to me) way to use SKIP LOCKED is wrong? Thanks! Harmen

Inserting many rows using "with"

can see Any thoughts? Thanks! Harmen