Hi again.
> Thinking some more on this, I now don't think a TODO makes sense, so I
> have removed it.
Please look into this example:
https://dbfiddle.uk/?rdbms=postgres_12&fiddle=95ed9fab6870d7c4b6266ea4d93def13
This is real life code from our production.
You can see that this is important to
Hello Eugen,
> https://dbfiddle.uk/?rdbms=postgres_12&fiddle=95ed9fab6870d7c4b6266ea4d93def13
sorry, forget to update link to the latest example:
https://dbfiddle.uk/?rdbms=postgres_12&fiddle=8e114ccc9f15a30ca3115cdc6c70d247
--
Best regards,
Eugen Konkov
Michael,
Thank you for your thoughtful reply. This might be much easier:
How about adding another example to
https://www.postgresql.org/docs/11/planner-stats.html ?
SELECT relname, seq_scan-idx_scan AS too_much_seq,
case when seq_scan-idx_scan>0 THEN 'Missing Index?' ELSE 'OK' END,
pg_rela
I recently ran afoul of the filters in the information schema views which
restrict the returned records to those entities the querying user has ownership
or any privilege on. The detailed documentation on the information schema does
mention this, e.g. in
https://www.postgresql.org/docs/current/