Re: Replacing plpgsql's lexer

From: Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Replacing plpgsql's lexer
Date: 2009-04-19 17:24:31
Message-ID: 1FD7BF1E-AFD4-4374-A0C1-4AA1D6A9349F@pointblue.com.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 19 Apr 2009, at 17:42, Tom Lane wrote:
>
> The attached proposed patch rips out plpgsql's handling of comments
> and
> string literals, and puts in scanner rules that are extracted from the
> core lexer (but simplified in a few places where we don't need all the
> complexity). The net user-visible effects should be:
>
>
> Comments?

Will it also mean, that queries are going to be analyzed deeper ?
Ie, afaik I am able now to create plpgsql function, that tries to run
query accessing non existent table, or columns.
Or, if I rename column/table/relation now, views, etc are getting
updated - but not plpgsql functions. Will that change with your patch ?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-04-19 17:28:49 Re: Replacing plpgsql's lexer
Previous Message Greg Stark 2009-04-19 17:18:32 Re: Replacing plpgsql's lexer