Thread: BUG #13777: FKs began to no longer treat referential integrity, ie, it was as if the FKs did not exist.

The following bug has been logged on the website:

Bug reference:      13777
Logged by:          Alvaro Neto
Email address:      alvaro.pereira.neto@gmail.com
PostgreSQL version: 9.3.6
Operating system:   RedHat 6.5 x86
Description:

We are experiencing a "bug" that we had not noticed, the releases 9.3.3 and
9.3.6.
  1) a migration via dump / restore, version 9.0.7 to version 9.3.6 was
carried out, and after seven months in one of the tables, which had 8 FKs,
these FKs began to no longer treat referential integrity, ie, it was as if
the FKs did not exist;
  2) the development platform, release 9.3.3, a database was created
(dbadmin-new) using, as a template, another existing database (dbadmin). And
then charges through inserts have not been validated by FKs. It was found
that all FKs exist. However, FKs not restricted any inclusion of information
without integrity. Instructions for creating the database was:
    CREATE DATABASE 'dbadmin-new' WITH TEMPLATE 'dbadmin' OWNER 'postgres'
TABLESPACE = 'homolog';

   Our PostgreSQL been compiled in accordance with the parameter set of the
following:
    * For 9.3.6 - production platform ==> CONFIGURE = '--prefix = / usr /
local / pgsql-9.3.6' --with-perl '' --with-python '' --with- tcl ''
--with-tclconfig = / usr / lib64 '' --with-krb5 '' --with-openssl ''
--with-pam '' --with-ldap '' --with-libxml '' --with-libxslt '
    * For 9.3.3 - plataform development ==> CONFIGURE = '--prefix'
'/usr/local/pgsql-9.3.3' '--with-perl' '--with-python' '--with -tcl ''
--with-tclconfig = / usr / lib64 '' --with-krb5 '' --with-openssl ''
--with-pam '' --with-ldap '' --with-libxml '--with-libxslt'

   Our production platform is grounded in PostgreSQL cluster with a total of
5 nodes, with streaming replication, and I am the one who created and
manages all of these platforms.

   You could refer, please, this e-mail to the development team to see if
anyone else has experienced this situation? Sought I and an architect,
references in this 'bug' but did not find anything or the forums, and even
the Internet in general.

  Thanks.

On 11/17/2015 11:14 AM, alvaro.pereira.neto@gmail.com wrote:
> We are experiencing a "bug" that we had not noticed, the releases 9.3.3 and
> 9.3.6.

those are both obsolete versions, 9.3.10 is the current release of the
9.3 system.   9.3.3 is from feb 2014, 9.3.6 is from february 2015.
there are extensive fix lists in each incremental version's release
notes between those versions and 9.3.10.    if you had installed from
the rpms at yum.postgresql.org, you could have simply done `yum update
postgresql93` to bring them up to current, but as you compiled your own
releases, it will take more work.

anyways, your bug report lacks sufficient detail to reproduce.

--
john r pierce, recycling bits in santa cruz