Re: libpq API incompatibility between 7.4 and 8.0

Martin Pitt wrote:
-- Start of PGP signed section.
> Hi!
> 
> Tom Lane [2005-02-04 10:27 -0500]:
> > This problem isn't worth spending more development time on than it takes
> > to change SO_MAJOR_VERSION (we have lots of higher-priority issues).
> 
> I just did that:
> 
> --- postgresql-8.0.1-old/src/interfaces/libpq/Makefile  2005-01-26 20:24:19.000000000 +0100
> +++ postgresql-8.0.1/src/interfaces/libpq/Makefile      2005-02-07 20:09:38.719686432 +0100
> @@ -16,8 +16,8 @@
> 
>  # shared library parameters
>  NAME= pq
> -SO_MAJOR_VERSION= 3
> -SO_MINOR_VERSION= 2
> +SO_MAJOR_VERSION= 4
> +SO_MINOR_VERSION= 0
>  DLTYPE= library
> 
>  override CPPFLAGS :=  -DFRONTEND -I$(srcdir) $(CPPFLAGS) -I$(top_builddir)/src/port
> 
> Is that right? Or will you use SO_MINOR_VERSION=1?

It would be zero.  I wouldn't distribute this until we actually release
it, but for testing I guess it is OK.

> However, I just stumbled across another problem: libpq3 and the new
> libpq4 use the same translation domain "libpq4", thus they cannot be
> installed in parallel. Can you please change the domain to "libpq4" as
> well? This should generally be done anyway, but at least we can live
> with one breakage of this rule (for libpq3), so that we don't need to
> mess with the old libpq3 package.

Uh, what is the translation domain?

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