Postgres 14

By using db<>fiddle, you agree to license everything you submit by Creative Commons CC0.

Help with an interesting Postgres question: Why isn't an Index Only Scan used on a partition accessed via the parent table?.

select version();

version

PostgreSQL 14.10 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-20), 64-bit

SELECT 1

CREATE TABLE test
(
  id INT GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
  t_field TEXT
);

CREATE TABLE

INSERT INTO test (t_field)
VALUES ('bar$foo$john$doe$xxx');  -- OP's own data

INSERT 0 1

INSERT INTO test (t_field)
SELECT 
  LEFT(MD5(RANDOM()::TEXT), FLOOR(RANDOM() * (5 - 3 + 1) + 3)::INT) || '$' ||
  LEFT(MD5(RANDOM()::TEXT), FLOOR(RANDOM() * (5 - 3 + 1) + 3)::INT) || '$' ||
  LEFT(MD5(RANDOM()::TEXT), FLOOR(RANDOM() * (5 - 3 + 1) + 3)::INT) || '$' ||
  LEFT(MD5(RANDOM()::TEXT), FLOOR(RANDOM() * (5 - 3 + 1) + 3)::INT) || '$' ||
  LEFT(MD5(RANDOM()::TEXT), FLOOR(RANDOM() * (5 - 3 + 1) + 3)::INT)
FROM 
  GENERATE_SERIES(1, 299999);  --<<== Vary here
   
  --
  -- Vary the GENERATE_SERIES(1, 299999) number if the fiddle run fails!
  --
  -- 299999 (+ 1 - OP) = 300,000 = large enough number to get reliable, consistent results
  -- and small enough so that the fiddle run doesn't fail too often.
  -- 

INSERT 0 299999

ANALYZE test;

ANALYZE

--
--
--
--
-- 3: Evan Carroll's solution.
--
-- REGEXP_REPLACE - only method that doesn't use REVERSE(). Elegant code-wise!
--

SELECT
  t_field,
  REGEXP_REPLACE(t_field, '(.*)\$', '\1-' )
FROM test
LIMIT 2;

t_field
regexp_replace

bar$foo$john$doe$xxx
bar$foo$john$doe-xxx

d1c3$bf6$e4762$79f52$37a
d1c3$bf6$e4762$79f52-37a

SELECT 2

EXPLAIN (ANALYZE, TIMING OFF)
SELECT
  REGEXP_REPLACE(t_field, '(.*)\$', '\1-' )
FROM test;

QUERY PLAN

Seq Scan on test  (cost=0.00..5969.00 rows=300000 width=32) (actual rows=300000 loops=1)

Planning Time: 0.024 ms

Execution Time: 483.047 ms

EXPLAIN

t_field	regexp_replace
bar$foo$john$doe$xxx	bar$foo$john$doe-xxx
d1c3$bf6$e4762$79f52$37a	d1c3$bf6$e4762$79f52-37a