From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: Edwin UY <edwin.uy@gmail.com>,
        "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: \i and \watch
In-reply-to: 
 <CAKFQuwZvMkCNffV8_X2yeVFJdOaFKwVUEuWcLpsvP-w+YjwBGw@mail.gmail.com>
References: 
 <CA+wokJ-NAMMVdo52WdwmGN8CasaE026jhRH7yb1MFU2eF=HeEw@mail.gmail.com>
 <CAKFQuwZvMkCNffV8_X2yeVFJdOaFKwVUEuWcLpsvP-w+YjwBGw@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Wed, 06 Nov 2024 22:26:53 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3414974.1730986982.1@sss.pgh.pa.us>
Date: Thu, 07 Nov 2024 08:43:02 -0500
Message-ID: <3414975.1730986982@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3414975.1730986982%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> Watch is documented to act on either a non-empty query buffer or the last
> sent command.  I would expect that whatever the final SQL command present
> in x.sql is would be the command that gets watched.  If indeed the
> preceding select 1 command is watched there would seem to be an
> undocumented interaction going on.

It looks like there's a separate query_buf for each recursive level
of MainLoop(), that is, each level of \i.  So maybe the docs need
improvement here.  (I think the actual behavior is probably fine.)

			regards, tom lane