Skip site navigation (1) Skip section navigation (2)

Re: libpq API incompatibility between 7.4 and 8.0

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martin Pitt <mpitt(at)debian(dot)org>
Subject: Re: libpq API incompatibility between 7.4 and 8.0
Date: 2005-02-03 14:42:18
Message-ID: 200502031442.j13EgIC07435@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Uh, if we bump up the major library version in 8.0.X, will that
> > require 8.0.0 user applications to be recompiled?
> 
> No, they just keep using the old library.

That assumes the old libraries stay around.  Will they?

I am thinking the easiest solution will be to re-add get_progname() to
8.0.X and bump the major for 8.1.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

Responses

pgsql-hackers by date

Next:From: Neil ConwayDate: 2005-02-03 14:42:48
Subject: Re: LWLock cache line alignment
Previous:From: Tom LaneDate: 2005-02-03 14:32:52
Subject: Re: LWLockRelease

pgsql-patches by date

Next:From: Heikki LinnakangasDate: 2005-02-03 15:34:28
Subject: Re: Refactoring lock.c
Previous:From: ITAGAKI TakahiroDate: 2005-02-03 10:25:55
Subject: Re: [PATCHES] WAL: O_DIRECT and multipage-writer (+ memory leak)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group