| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, 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 00:30:15 |
| Message-ID: | 4D338D97.4070001@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2011-01-17 00:32:55 | Re: Spread checkpoint sync |
| Previous Message | Robert Haas | 2011-01-17 00:23:43 | Re: READ ONLY fixes |