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
Re: Add comments about fire_triggers argument in ri_triggers.c - Mailing list pgsql-hackers
From
surya poondla
Subject
Re: Add comments about fire_triggers argument in ri_triggers.c
Date
January 29
03:56:19
Msg-id
CAOVWO5q8cfbHiZuL-wSxknnriPCBYpqRCnQKfH38WuLwFuxkSw@mail.gmail.com
Whole thread
Raw
In response to
Add comments about fire_triggers argument in ri_triggers.c
(Yugo Nagata <nagata@sraoss.co.jp>)
List
pgsql-hackers
Tree view
Hi Yugo,
Your patch change looks good.
Yes Amit, I agree that SPI_execute_snapshot() comments do provide some context on AFTER triggers, but I still feel the newly added comment in ri_PerformCheck() gives additional context on why the fire_triggers is set to false.
Regards,
Surya Poondla
pgsql-hackers
by date:
Previous
From:
Michael Paquier
Date:
29 January, 03:32:14
Subject:
Re: psql: make %P prompt option consistent when not connected
Next
From:
Heikki Linnakangas
Date:
29 January, 04:05:33
Subject:
Re: Interrupts vs signals
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
×
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