pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Oleksandr Shulgin <oleksandr.shulgin@zalando.de>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Jobin Augustine <jobinau@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: libpq parameter parsing problem
Date: Fri, 17 Jan 2020 15:29:45 +0900
Message-ID: <20200117062945.GJ2127@paquier.xyz> (raw)
In-Reply-To: <CACACo5RmzPraKgrpcQrWLC782ViHF06NOScBLYnj5WqhcY2WwA@mail.gmail.com>
References: <CANaTPsrYgSgE2fuj3=4x=Jmx1c+NgkEDzftNknZbrMuqL+aBhQ@mail.gmail.com>
	<CACACo5Qf4xBbs=8s4sYxZiQEYzfKM3JY3uCDrtZYu3CpOcP5xA@mail.gmail.com>
	<CANaTPsrgsrVK2nb6bPym-fZcQvL7aJErMCXek7LBp-QFDQt-RQ@mail.gmail.com>
	<22b4a79a-5d60-cec0-474e-4a68c8be2b7a@iki.fi>
	<20200109043809.GK2251@paquier.xyz>
	<CANaTPsqq17XvXDsrm4J6GXZqnNw=0=Y+txMRyBBTJn4sGJw9ig@mail.gmail.com>
	<20200114060317.GF1515@paquier.xyz>
	<fe1a7b9f-5630-00dd-3780-1b150a583fdf@2ndquadrant.com>
	<20200116034917.GD3117@paquier.xyz>
	<CACACo5RmzPraKgrpcQrWLC782ViHF06NOScBLYnj5WqhcY2WwA@mail.gmail.com>

On Thu, Jan 16, 2020 at 09:17:23AM +0100, Oleksandr Shulgin wrote:
> At the same time, we could still be more specific if we would say
> "delimiters" instead of the generic "special meaning".  Should we then
> provide an exhaustive list of delimiters or is it clear enough like that?
> For example, the whitespace doesn't need to be percent-encoded (it doesn't
> hurt as you might be able to spare the quoting if using it as an argument
> to a shell command), while the "equal sign", when used in the query string
> part, does need encoding.

This term comes from you, as of 2d612ab, and that does not look like
something to change because reserved characters have "sometimes" a
special meaning in this context.  A reference to the RFC is sufficient
IMO, readers could always look at that reference for a precise list
and that would bloat the docs more than necessary.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (22+ messages)  latest in thread

Message-ID: <20200117062945.GJ2127@paquier.xyz>
Permalink:  ../20200117062945.GJ2127@paquier.xyz/
Also on:    postgresql.org/message-id/20200117062945.GJ2127@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: michael@paquier.xyz, oleksandr.shulgin@zalando.de, peter.eisentraut@2ndquadrant.com, jobinau@gmail.com, hlinnaka@iki.fi
  Subject: Re: libpq parameter parsing problem
  In-Reply-To: <20200117062945.GJ2127@paquier.xyz>
  References: <CANaTPsrYgSgE2fuj3=4x=Jmx1c+NgkEDzftNknZbrMuqL+aBhQ@mail.gmail.com> <CACACo5Qf4xBbs=8s4sYxZiQEYzfKM3JY3uCDrtZYu3CpOcP5xA@mail.gmail.com> <CANaTPsrgsrVK2nb6bPym-fZcQvL7aJErMCXek7LBp-QFDQt-RQ@mail.gmail.com> <22b4a79a-5d60-cec0-474e-4a68c8be2b7a@iki.fi> <20200109043809.GK2251@paquier.xyz> <CANaTPsqq17XvXDsrm4J6GXZqnNw=0=Y+txMRyBBTJn4sGJw9ig@mail.gmail.com> <20200114060317.GF1515@paquier.xyz> <fe1a7b9f-5630-00dd-3780-1b150a583fdf@2ndquadrant.com> <20200116034917.GD3117@paquier.xyz> <CACACo5RmzPraKgrpcQrWLC782ViHF06NOScBLYnj5WqhcY2WwA@mail.gmail.com> <20200117062945.GJ2127@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox