Horton

Re: EXECUTE tab completion

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Kupershmidt <schmiddy@gmail.com>
Cc: Andreas Karlsson <andreas@proxel.se>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-10-20T02:40:25Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add ALTER TABLE ... ALTER COLUMN ... SET STATISTICS DISTINCT

Josh Kupershmidt <schmiddy@gmail.com> writes:
> Incidentally, I was wondering what the heck was up with a clause like this:
>     else if (pg_strcasecmp(prev_wd, "EXECUTE") == 0 &&
>              pg_strcasecmp(prev2_wd, "EXECUTE") == 0)

Hmm, maybe || was meant not && ?  It seems pretty unlikely that the
above test would ever trigger on valid SQL input.

			regards, tom lane