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
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
Cloud Solutions
Postgres Extensions
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
Fix misuse use of window_gettupleslot function (src/backend/executor/nodeWindowAgg.c) - Mailing list pgsql-hackers
From
Ranier Vilela
Subject
Fix misuse use of window_gettupleslot function (src/backend/executor/nodeWindowAgg.c)
Date
October 5
16:23:58
Msg-id
CAEudQArGABt_KKhZiwcKD1gYs3AzburecdoVK7hGUjqa7xqrFQ@mail.gmail.com
Whole thread
Raw
Responses
Re: Fix misuse use of window_gettupleslot function (src/backend/executor/nodeWindowAgg.c)
List
pgsql-hackers
Tree view
Hi.
Per Coverity.
CID 1635309: (#1 of 1): Unchecked return value (CHECKED_RETURN)
7.
check_return:
Calling window_gettupleslot without checking return value (as is done elsewhere 8 out of 9 times).
The function "window_gettupleslot" can fail.
All other calls check the return, In this case it could not be different.
Fix by checking the return and reporting a message to the user,
in case of failure.
The error message, however, I'm not sure if it's ideal.
best regards,
Ranier Vilela
Attachment
fix-api-misuse-function-window_gettupleslot.patch
pgsql-hackers
by date:
Previous
From:
Jim Jones
Date:
05 October, 13:02:10
Subject:
Re: We broke the defense against accessing other sessions' temp tables
Next
From:
"Euler Taveira"
Date:
05 October, 17:18:53
Subject:
Re: log_min_messages per backend type
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
×
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
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