Your message dated Tue, 18 Feb 2014 13:58:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#739393: postgresql-9.3: Documented type “json” does
not exist
has caused the Debian Bug report #739393,
regarding postgresql-9.3: Documented type “json” does not exist
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
739393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739393
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-9.3
Version: 9.3.2-1
Severity: normal
Dear Maintainer,
The documentation specifies that the “json” type is built in, see
‘/usr/share/doc/postgresql-doc-9.3/html/datatype-json.html’. However, when
I try to use this type, the server tells me it doesn't exist:
=====
$ psql
bignose@[local] ~=> CREATE TABLE foo (
bignose@[local] ~(> id integer NOT NULL,
bignose@[local] ~(> spam json NOT NULL,
bignose@[local] ~(> PRIMARY KEY (id)
bignose@[local] ~(> );
ERROR: type "json" does not exist
LINE 3: spam json NOT NULL,
=====
Please enable the “json” type in the server as a built-in type, as documented.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages postgresql-9.3 depends on:
ii libc6 2.17-97
ii libcomerr2 1.42.9-3
ii libgssapi-krb5-2 1.12+dfsg-2
ii libkrb5-3 1.12+dfsg-2
ii libldap-2.4-2 2.4.31-1+nmu2+b1
ii libpam0g 1.1.3-9
ii libpq5 9.3.2-1
ii libssl1.0.0 1.0.1f-1
ii libxml2 2.9.1+dfsg1-3
ii locales 2.17-97
ii postgresql-client-9.3 9.3.2-1
ii postgresql-common 153
ii ssl-cert 1.0.33
ii tzdata 2013i-1
postgresql-9.3 recommends no packages.
Versions of packages postgresql-9.3 suggests:
pn locales-all <none>
ii pidentd [ident-server] 3.0.19.ds1-7
-- no debconf information
--
\ “Guaranteed to work throughout its useful life.” —packaging for |
`\ clockwork toy, Hong Kong |
_o__) |
Ben Finney <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Re: Ben Finney 2014-02-18 <[email protected]>
> > Are you sure that was a 9.3 server?
>
> Hmm, I have ‘postgresql-9.3’ installed but I didn't realise
> ‘postgresql-9.1’ is still installed.
9.1 was still listening on port 5432, so you were connecting to this
cluster because that's the default port.
> Both packages are marked auto-installed, and I only want whatever is the
> latest PostgreSQL installed.
>
> When I remove the ‘postgresql-9.1’ package, no dependencies are broken.
> (And this bug report's behaviour no longer occurs.)
9.3 is on 5433, and when the 9.1 cluster is gone/inaccessible,
pg_wrapper will direct you to this port.
> The ‘postgresql-9.1’ package is not needed for any dependencies, and it is
> marked for auto-removal when no longer needed. So why wasn't it
> automatically removed?
Apt doesn't know if you have any data in the old 9.1 cluster that you
might want to upgrade before removing the old packages. That's why we
put postgresql.* in /etc/apt/apt.conf.d/01autoremove-postgresql.
(You could argue that you wouldn't invoke apt-get autoremove without
checking what packages actually get removed, but people aren't that
smart in general.)
Christoph
--
[email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-postgresql-public mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
