Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Postgres Pro Shardman
Postgres Pro Enterprise Manager
Postgres Pro ProGate
Cloud Solutions
Postgres Extensions
Cases
Courses
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Postgres Pro Shardman
Postgres Pro Enterprise Manager
Postgres Pro ProGate
Cloud Solutions
Postgres Extensions
Cases
Courses
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Request a Demo
Home
>
mailing lists
[GENERAL] UPDATE column without FK fires other FK triggers constraint check - Mailing list pgsql-general
From
Luca Looz
Subject
[GENERAL] UPDATE column without FK fires other FK triggers constraint check
Date
July 18, 2017
15:49:10
Msg-id
CAHXaXTw_2va3Dk9oT0KpEq9-t-c1MMAm0YOLhtU6ER4M31+wSw@mail.gmail.com
Whole thread
Responses
Re: [GENERAL] UPDATE column without FK fires other FK triggers constraint check
List
pgsql-general
Tree view
I was analyzing an update function and i have noticed "Trigger for constraint" entries for foreign keys that i wasn't using or referring.
After some tests it seems that this happens when the same row is covered by more than 1 update in the same transaction even without any change.
Here is a dbfiddle example:
http://dbfiddle.uk/?rdbms=postgres_9.6&fiddle=368289a7338031b8a7b7a90f0fd25d7c
Is this an expected behavior? Why it happens?
I have initially asked this on dba stackexchange:
https://dba.stackexchange.com/questions/180012/
pgsql-general
by date:
Previous
From:
basti
Date:
18 July 2017, 12:13:47
Subject:
Re: [GENERAL] log_filename
Next
From:
Mikhail
Date:
18 July 2017, 17:21:39
Subject:
[GENERAL] Index Only Scan and Heap Fetches
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
×
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Postgres Pro Shardman
Postgres Pro Enterprise Manager
Postgres Pro ProGate
Cloud Solutions
Postgres Extensions
Cases
Courses
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies