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
ereport bug - Mailing list pgsql-hackers
From
Dmitry Voronin
Subject
ereport bug
Date
January 12, 2015
11:27:43
Msg-id
43691421062049@web19g.yandex.ru
Whole thread
Responses
Re: ereport bug
Re: ereport bug
List
pgsql-hackers
Tree view
Hello, postgresmen!
I found incorrect execution of ereport() macro.
If we pass into ereport() function 2 or more arguments, the macro errcontext does not correct execute. So, ereport() call stack is:
errstart
errcontext_msg
set_errcontext_domain
errmsg
errfinish
pg_unreachable
This bug
causes that error messages (for example, in PL/TCL) are
not localized.
Solutions:
- Wrap all errcontext() macro in
brackets, that is errcontext("error message %s", "end message") -> (
errcontext("error message %s", "end message"))
- Rewrite this macro
- ???
I am attaching
to this letter
a test case
that shows
the behavior errcontext() macro and the way to fix it.
I am using postgresql 9.4 and test it on gcc 4.7 and gcc 4.8.1.
-- Best regards, Dmitry Voronin
pgsql-hackers
by date:
Previous
From:
Ashutosh Bapat
Date:
12 January 2015, 09:36:26
Subject:
Re: Async execution of postgres_fdw.
Next
From:
Dean Rasheed
Date:
12 January 2015, 12:28:34
Subject:
Re: INSERT ... ON CONFLICT UPDATE and RLS
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
×
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