Drop support for Python 2.3
There is no specific reason for this right now, but keeping support for
old Python versions around indefinitely increases the maintenance
burden. The oldest supported Python version is now Python 2.4, which is
still shipped in RHEL/CentOS 5 by default.
In configure, a
On Tue, Oct 11, 2016 at 04:19:26PM +, Tom Lane wrote:
> Drop server support for FE/BE protocol version 1.0.
Yay!
Best,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember
Drop server support for FE/BE protocol version 1.0.
While this isn't a lot of code, it's been essentially untestable for
a very long time, because libpq doesn't support anything older than
protocol 2.0, and has not since release 6.3. There's no reason to
believe any other client-side code still u
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database
DROP OWNED: don't try to drop tablespaces/databases
My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only
misstated that it applied to REASSIGN OWNED (which it did not affect),
but it also failed to fix the problems fully, because I didn't test the
case of owned shared objects.
DROP OWNED: don't try to drop tablespaces/databases
My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only
misstated that it applied to REASSIGN OWNED (which it did not affect),
but it also failed to fix the problems fully, because I didn't test the
case of owned shared objects.
DROP OWNED: don't try to drop tablespaces/databases
My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only
misstated that it applied to REASSIGN OWNED (which it did not affect),
but it also failed to fix the problems fully, because I didn't test the
case of owned shared objects.
DROP OWNED: don't try to drop tablespaces/databases
My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only
misstated that it applied to REASSIGN OWNED (which it did not affect),
but it also failed to fix the problems fully, because I didn't test the
case of owned shared objects.
DROP OWNED: don't try to drop tablespaces/databases
My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only
misstated that it applied to REASSIGN OWNED (which it did not affect),
but it also failed to fix the problems fully, because I didn't test the
case of owned shared objects.
DROP OWNED: don't try to drop tablespaces/databases
My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only
misstated that it applied to REASSIGN OWNED (which it did not affect),
but it also failed to fix the problems fully, because I didn't test the
case of owned shared objects.
Drop cheap-startup-cost paths during add_path() if we don't need them.
We can detect whether the planner top level is going to care at all about
cheap startup cost (it will only do so if query_planner's tuple_fraction
argument is greater than zero). If it isn't, we might as well discard
paths imm
Drop "meaning" column from error code table
This is currently the same as the condition name, so it doesn't add
any value, only clutter.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/420dcaaeb1a3be51b6417da59ce69d7954369211
Modified Files
--
doc/src/sg
Log Message:
---
DROP IF EXISTS for columns and constraints. Andres Freund.
Modified Files:
--
pgsql/doc/src/sgml/ref:
alter_table.sgml (r1.106 -> r1.107)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_table.sgml?r1=1.106&r2=1.107)
Log Message:
---
Drop CLI related features from the list, since we don't track the ODBC
business in core.
Modified Files:
--
pgsql/src/backend/catalog:
sql_features.txt (r1.35 -> r1.36)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/sql
Log Message:
---
Drop indentation of verbatim environments in print output. This increased
the build time by what seemed like infinity.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
stylesheet.dsl (r1.30 -> r1.30.2.1)
(http://developer.p
Log Message:
---
Drop indentation of verbatim environments in print output. This increased
the build time by what seemed like infinity.
Modified Files:
--
pgsql/doc/src/sgml:
stylesheet.dsl (r1.30 -> r1.31)
(http://developer.postgresql.org/cvsweb.cgi/pgsql
Neil Conway wrote:
On Fri, 2006-06-16 at 17:23 -0300, Andrew Dunstan wrote:
DROP ... IF EXISTS for the following cases:
language, tablespace, trigger, rule, opclass, function, aggregate. operator,
and cast.
Documentation?
-Neil
It's coming. I just wanted to make sure I didn
On Fri, 2006-06-16 at 17:23 -0300, Andrew Dunstan wrote:
> DROP ... IF EXISTS for the following cases:
> language, tablespace, trigger, rule, opclass, function, aggregate.
> operator, and cast.
Documentation?
-Neil
---(end of broadcast)---
TIP
Log Message:
---
DROP ... IF EXISTS for the following cases:
language, tablespace, trigger, rule, opclass, function, aggregate. operator,
and cast.
Modified Files:
--
pgsql/src/backend/commands:
aggregatecmds.c (r1.34 -> r1.35)
(http://developer.postgre
Log Message:
---
DROP IF EXISTS for ROLE/USER/GROUP
Modified Files:
--
pgsql/doc/src/sgml/ref:
drop_group.sgml (r1.11 -> r1.12)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_group.sgml.diff?r1=1.11&r2=1.12)
drop_role.sgml
Log Message:
---
DROP DATABASE IF EXISTS variant
Modified Files:
--
pgsql/doc/src/sgml/ref:
drop_database.sgml (r1.20 -> r1.21)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/drop_database.sgml.diff?r1=1.20&r2=1.21)
pgsql/src/backe
Log Message:
---
DROP objecttype IF EXISTS for the following objects:
table view index sequence schema type domain conversion
Modified Files:
--
pgsql/doc/src/sgml/ref:
drop_conversion.sgml (r1.8 -> r1.9)
(http://developer.postgresql.org/cvsweb.cgi/pgsql
27 matches
Mail list logo
