[Pkg-postgresql-public] pgpool2 REMOVED from testing

[Debian testing watch]

FYI: The status of the pgpool2 source package
in Debian's testing distribution has changed.

  Previous version: 3.5.4-2
  Current version:  (not in testing)
  Hint: 
Bug #828497: pgpool2: FTBFS with openssl 1.1.0

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] how to get a local/minimal per-user postgresql server on debian?

[Christoph Berg]

Re: Daniel Kahn Gillmor 2016-11-11 <87wpgafb5a@alice.fifthhorseman.net>
> Thanks for the pointers, i think this gives me enough to chew on for the
> moment.  These suggestions don't really help with minimizing the
> dependency chain, of course, but that sort of "postgresql-light" rebuild
> might not be worth the effort.

I don't think it would be. The "extra dependency" footprint of
postgresql-N.N on a typical system is often zero (e.g. libldap is
often already there anyway), and even postgresql-contrib-N.N will only
pull very few extra libraries. I'm even pondering fully merging the
contrib package into the main server package, but haven't decided yet.

Thanks for your input!

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] how to get a local/minimal per-user postgresql server on debian?

[Christoph Berg]

Re: Daniel Kahn Gillmor 2016-11-10 <8737iz5klm@alice.fifthhorseman.net>
> Hi Debian PostgreSQL folks--
> 
> Thre are some circumstances where i'd like to have the postgresql
> binaries available without necessarily needing the system services
> installed and started.  For example, i have a set of intermittent
> short-lived processes that need to share long-lived state.  The state is
> best described as a relational database, but i want all that state to be
> under control of the unix user account that executes the processes, and
> not under control of some other system user like postgres.

Hi,

PG is not going to be an embedded database, so there will never be
something like a libpostgresql that you could link to and have the DB
"inside" your program. It will always be a (set of) separate
processes. Which means you'll need infrastructure to "boot" it.

postgresql-common supports "user clusters", i.e. you can point
PG_CLUSTER_CONF_ROOT to some place where the config should be, and
also ask for the data directory to be elsewhere. I haven't tested how
compatible this is with "user" systemd instances, but it's probably
not too hard to get it running. (See pg_wrapper(1).)

Also, I'm not sure why you would want to avoid the dependency on
postgresql-common, if you don't want the service files or pg_*cluster,
just don't use it? (If you want to avoid the "main" cluster to be
created on postgresql-N.N install, add "create_main_cluster = false"
to /etc/postgresql-common/createcluster.conf before installing the package.)

I'm not sure this answers all of your questions, but before I'm
answering everything from the wrong perspective, does this address
your use case?

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public