| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, fgp(at)phlo(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: LOCK for non-tables |
| Date: | 2011-01-17 01:12:15 |
| Message-ID: | 1295226735.3282.1845.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2011-01-16 at 16:30 -0800, Ron Mayer wrote:
> Tom Lane wrote:
> > Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> >> It's a major undertaking trying to write software that runs against
> >> PostgreSQL for more than one release. We should be making that easier,
> >> not harder.
> >
> > None of the proposals would make it impossible to write a LOCK statement
> > that works on all available releases, [....]
>
> +1 for this as a nice guideline/philosophy for syntax changes in general.
Thanks Tom, appreciate it.
> Personally I don't mind changing a few SQL statements when I upgrade
> to a new release; but it sure is nice if there's at least some syntax
> that works on both a current and previous release.
Yes, changing to a form of syntax that is then both backwards and
forwards compatible is a good solution.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Hunsaker | 2011-01-17 01:14:09 | Re: plperlu problem with utf8 [REVIEW] |
| Previous Message | Fujii Masao | 2011-01-17 01:07:16 | Re: auto-sizing wal_buffers |