News for hackers. Stuff that matters.
Re:Working around a case where the Postgres planner is “not ... by asah on Monday August 02, 2021 @04:28PM (#28042195)
2c: in most cases, a Postgres index is (performance wise) identical to a "real column" just without the name, and indeed you have more control over the data structure for an index, and indexes can include lossy compression (e.g. partial indexes) unlike a real column...

(obviously, the challenge is getting pg to use your index for a given query... for that, I like to use VIEWs to help query authors write queries that use the indexes)

Re:Working around a case where the Postgres planner is “not ... by saurik on Tuesday August 03, 2021 @12:12AM (#28045641)
Yeah. This wasn't the case a while back--PostgreSQL was missing support for what I think people call covered indexes, and so would only use the index to filter a set of candidate rows and then still had to go digging around in the real tuple to verify it matched--but I am pretty sure they changed that a while back.