Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1Y7o-0000N6-GB for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 14:01:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1Y7m-0002NX-Mm for pgsql-docs@arkaria.postgresql.org; Thu, 29 Mar 2018 14:01:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1Y7m-0002NN-AP for pgsql-docs@lists.postgresql.org; Thu, 29 Mar 2018 14:01:54 +0000 Received: from mail-qt0-x242.google.com ([2607:f8b0:400d:c0d::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1f1Y7j-0006QV-8W; Thu, 29 Mar 2018 14:01:53 +0000 Received: by mail-qt0-x242.google.com with SMTP id h4so6286453qtn.13; Thu, 29 Mar 2018 07:01:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lX5YHB83leUX+P22DPIEhhyt5ShanGKjlUDoKhA9yuU=; b=FSWtmY9b7mJUcmvE7PjIQZGZCNIcZtqFhBNkN9u5T7LAMdlepAtqR7lX+Ou+8qPrJW HbruZZ495xE00LXRfDEAzFIGJbChUG2ZOXeO+xka3eKVgK7OFWWGNta+50LHLv0Ao8OK g9wum0REXfyGg10zRQnm7DELAaBq8W0JWeUAfPfQA17ZnwOtCU77C88lIWnOZDpw41Fi yieWnrfGiO9tcU1ZE8JB7uWgAQV1OIqoMhrFOI/AkHZlPVNqij5Zp+BrtbBW4+T2IzlP k3iT+LR3VHUkMEflpal8tL0OY9Zu4Z4HAcKab0wa1tMRxekRYI/78ryWxBxHbnsKICdf 1/zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lX5YHB83leUX+P22DPIEhhyt5ShanGKjlUDoKhA9yuU=; b=i7bx+QeRjAfuG2fM568wDZ7CmDpYmC74t796DMeaMrUqZV81RbHjNLdb67zW1g963J VWOW+Zp1djXOc6O3RZBTWVk8B542F+2D4KYzjuoDjr1/OwpPlcNby+MAL7z6A6hCNAz1 bumIHj8YPF68AJbAoxLJzjYzmEdqcHb0gT5nJMvGXWyFj/9a5bbHKpE7JFA8nPsmuGpC oojzTYgjCObJhvM1Vs+P4PiQddEuE9BdI9eBoSYcBL+7cSfDD+z4SKPp24x7olqmShrJ QAY/W4A9uY55f9kfrmHiWKTZ1y2zG1jD9W1l8K54mX74vxJkNexGtVNw0uySkHtufbS6 7u6g== X-Gm-Message-State: ALQs6tBbtsU5Dv+e6551+6m5c3XOKUfvYfLCPGtqyfGDq6sovXcy+dez Vrq2mSNXdANKqsfjlcYD5gtMD8ReSpWtIP77ouw= X-Google-Smtp-Source: AIpwx48KRBytFVYVXJ+9NLf4pl03qqgbEGie5GimkNiGWqd5AW9JlHXOwk1gidh3SAlhPPti17jXtuFwlsD3nwV4NIE= X-Received: by 10.200.46.139 with SMTP id h11mr11671876qta.253.1522332110180; Thu, 29 Mar 2018 07:01:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.157.78 with HTTP; Thu, 29 Mar 2018 07:01:49 -0700 (PDT) In-Reply-To: <13425.1522330858@sss.pgh.pa.us> References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com> <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org> <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org> <13425.1522330858@sss.pgh.pa.us> From: "David G. Johnston" Date: Thu, 29 Mar 2018 07:01:49 -0700 Message-ID: Subject: Re: Blanks in the first line before the first word in the code boxes To: Tom Lane Cc: Magnus Hagander , "Jonathan S. Katz" , Peter Eisentraut , Daniel Westermann , pgsql-docs Content-Type: multipart/alternative; boundary="001a11c10f90a8588105688d90aa" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a11c10f90a8588105688d90aa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 29, 2018 at 6:40 AM, Tom Lane wrote: > Magnus Hagander writes: > > Is it possible that this issue actually showed up around 4-5 February, > but > > just has gone unnoticed since? > > It's been there a few weeks, anyway --- I remember somebody complaining > before this particular thread started. I wouldn't be a bit surprised > if it broke then. > =E2=80=8BFirst report that both Tom and I responded to, Tom by cc'ing www, = was on the Feb 26th, https://www.postgresql.org/message-id/151965261562.21248.680702308554136126= 4%40wrigleys.postgresql.org David J. --001a11c10f90a8588105688d90aa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Ma= r 29, 2018 at 6:40 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@h= agander.net> writes:
> Is it possible that this issue actually showed up around 4-5 February,= but
> just has gone unnoticed since?

It's been there a few weeks, anyway --- I remember somebody comp= laining
before this particular thread started.=C2=A0 I wouldn't be a bit surpri= sed
if it broke then.

=E2=80=8BFirst report t= hat both Tom and I responded to, Tom by cc'ing www, was on the Feb 26th= ,

https://www.= postgresql.org/message-id/151965261562.21248.6807023085541361264%40wrigleys= .postgresql.org

David J.

<= /div>
--001a11c10f90a8588105688d90aa--