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
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
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
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
Add schema-qualified relnames in constraint error messages. - Mailing list pgsql-hackers
From
Petr Korobeinikov
Subject
Add schema-qualified relnames in constraint error messages.
Date
January 6, 2016
01:00:14
Msg-id
CAJL5ff_XSMLL+MZNAaw8nisyLrUfO_UfOde4M3ZodWcoGE-Njg@mail.gmail.com
Whole thread
Raw
Responses
Re: Add schema-qualified relnames in constraint error messages.
List
pgsql-hackers
Tree view
Hackers,
At the moment schemas used as single-level namespaces.
It's quite convenient in large databases.
But error messages doesn’t contain schema names.
I have done a little patch with schema-qualified relation names in error messages that produced by foreign key constraints and triggers.
Patch and usage example are attached.
Based on real bug hunting.
Pre-reviewed by Alexander Korotkov.
Attachment
namespaced-relname.diff
example.sql
pgsql-hackers
by date:
Previous
From:
Michael Paquier
Date:
06 January 2016, 00:53:13
Subject:
Re: No Issue Tracker - Say it Ain't So!
Next
From:
Tom Lane
Date:
06 January 2016, 01:02:23
Subject:
Re: pg_conversion seems rather strangely defined
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
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
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
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