Fix comment of tsquerysend()
authorÁlvaro Herrera <[email protected]>
Sun, 11 May 2025 13:47:10 +0000 (09:47 -0400)
committerÁlvaro Herrera <[email protected]>
Sun, 11 May 2025 13:47:10 +0000 (09:47 -0400)
The comment describes the order in which fields are sent, and it had one
of the fields in the wrong place.

This has been wrong since e6dbcb72fafa (2008), so backpatch all the way
back.

Author: Emre Hasegeli <[email protected]>
Discussion: https://postgr.es/m/CAE2gYzzf38bR_R=izhpMxAmqHXKeM5ajkmukh4mNs_oXfxcMCA@mail.gmail.com

src/backend/utils/adt/tsquery.c

index b1bad7bd60cf5e4d5739364f5bfffba8211dbfa4..717de8073d58dbbba2c163b0b54d60fe96f2962f 100644 (file)
@@ -1176,10 +1176,11 @@ tsqueryout(PG_FUNCTION_ARGS)
  *
  * uint8   type, QI_VAL
  * uint8   weight
- *         operand text in client encoding, null-terminated
  * uint8   prefix
+ *         operand text in client encoding, null-terminated
  *
  * For each operator:
+ *
  * uint8   type, QI_OPR
  * uint8   operator, one of OP_AND, OP_PHRASE OP_OR, OP_NOT.
  * uint16  distance (only for OP_PHRASE)