On Wed, Dec 02, 2020 at 12:58:36PM -0500, Stephen Frost wrote: > Greetings, > > * Peter Eisentraut (peter.eisentr...@enterprisedb.com) wrote: > > While reading about deprecating and removing various things in > > other threads, I was wondering about how deprecated SELECT INTO > > is. There are various source code comments about this, but the > > SELECT INTO reference page only contains soft language like > > "recommended". I'm proposing the attached patch to stick a more > > explicit deprecation notice right at the top. > > I don't see much value in this. Users already have 5 years to adapt > their code to new major versions of PG and that strikes me as plenty > enough time and is why we support multiple major versions of PG for > so long. Users who keep pace and update for each major version > aren't likely to have issue making this change since they're already > used to regularly updating their code for new major versions, while > others are going to complain no matter when we remove it and will > ignore any deprecation notices we put out there, so there isn't much > point in them.
+1 for removing it entirely and including this prominently in the release notes. Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
