Skip site navigation (1) Skip section navigation (2)

Re: hstore parser incorrectly handles malformed input

From: Vik Reykja <vikreykja(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ryan Kelly <rpkelly22(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: hstore parser incorrectly handles malformed input
Date: 2012-04-27 09:27:03
Message-ID: CALDgxVsZfSoWxHxpzsH22heJqwb6aom5x8kmVVe4WVq-fwTtOQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Apr 27, 2012 at 03:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Does anybody else have an opinion as to which of these solutions is
> more preferable?
>

I think all unquoted whitespace should be ignored, so I prefer your
solution. (note: I haven't actually tested it, I'm going off these emails)


> And should we regard this as a back-patchable bug
> fix, or a definition change suitable only for HEAD?
>

Since this is removing a syntax error and not creating one, I'd say it
should be safe to backpatch.

In response to

Responses

pgsql-bugs by date

Next:From: Ryan KellyDate: 2012-04-27 11:22:35
Subject: Re: hstore parser incorrectly handles malformed input
Previous:From: petteri.ratyDate: 2012-04-27 07:47:50
Subject: BUG #6619: Misleading output from slave when host is not running

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group