5 ms·
Using the hint table has been pretty painful, in my experience. Two main difficulties I’ve seen: 1. The hint patterns are whitespace-sensitive. Accidentally put
by IvanVergiliev 3y ago
Using the hint table has been pretty painful, in my experience. Two main difficulties I’ve seen:
1. The hint patterns are whitespace-sensitive. Accidentally put a tab instead of a couple of spaces, and you get a silent match failure.
2. There are different ways to encode query parameters - `?` for literals in the query text, `$n` for query parameters. Psql / pgcli don’t support parameterized queries so you can’t use them to iterate on your hints.
Still super useful when you have no other options though.
- IsTom 3y ago> Psql / pgcli don’t support parameterized queries so you can’t use them to iterate on your hints. Isn't this what PREPARE and EXECUTE does?
- feike 3y agoYou should be able nowadays with PG16 INSERT INTO tbl1 VALUES ($1, $2) \bind 'first value' 'second value' \g https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-META-COMMAND-BIND https://www.postgresql.org/docs/current/app-psql.html#APP-PS... For older versions, you can do: \set v_x 'first value' \set v_y 'second value' INSERT INTO tbl1 VALUES (:'v_x', :'v_y'); \set v_x 'next value' INSERT INTO tbl1 VALUES (:'v_x', :'v_y');