postgres=# select * from sessions where video_id = 'VKuxQZlvd8E';

Command-tag customization

· 94:41 · SQL & client

Custom protocol command tags and _pq_ capability negotiation.

session summary

After testing the newly committed REPACK command and confirming that it is transactional but takes an access-exclusive lock, the group built a prototype for customizable command-completion tags such as schema-qualified table names. A first server-only change broke psql's parser, exposing the need for client/server capability negotiation. The agent then used the existing _pq_ protocol-options framework so only requesting clients receive the new format. They reviewed compatibility tests and concluded the patch was useful for discussion but needed cleanup before pgsql-hackers.

timecodes

  1. Testing the new REPACK command
  2. REPACK locking and transaction behavior
  3. Designing descriptive command tags
  4. Prototype-first agentic implementation
  5. Server-only format change breaks psql
  6. Why protocol feature negotiation is required
  7. Using the _pq_ protocol-options framework
  8. Compatibility review and patch cleanup