pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone 5+ messages / 1 participants [nested] [flat]
* pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone @ 2022-08-01 07:40 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 5+ messages in thread From: Michael Paquier @ 2022-08-01 07:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix error reporting after ioctl() call with pg_upgrade --clone errno was not reported correctly after attempting to clone a file, leading to incorrect error reports. While scanning through the code, I have not noticed any similar mistakes. Error introduced in 3a769d8. Author: Justin Pryzby Discussion: https://postgr.es/m/20220731134135.GY15006@telsasoft.com Backpatch-through: 12 Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/24872bbf9288d8949b3f2ed60c0f3ef12015016f Modified Files -------------- src/bin/pg_upgrade/file.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone @ 2022-08-01 07:40 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 5+ messages in thread From: Michael Paquier @ 2022-08-01 07:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix error reporting after ioctl() call with pg_upgrade --clone errno was not reported correctly after attempting to clone a file, leading to incorrect error reports. While scanning through the code, I have not noticed any similar mistakes. Error introduced in 3a769d8. Author: Justin Pryzby Discussion: https://postgr.es/m/20220731134135.GY15006@telsasoft.com Backpatch-through: 12 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/aadaaeff4cf8b90c62dbb6cc67f5dd7e5a0297fe Modified Files -------------- src/bin/pg_upgrade/file.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone @ 2022-08-01 07:40 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 5+ messages in thread From: Michael Paquier @ 2022-08-01 07:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix error reporting after ioctl() call with pg_upgrade --clone errno was not reported correctly after attempting to clone a file, leading to incorrect error reports. While scanning through the code, I have not noticed any similar mistakes. Error introduced in 3a769d8. Author: Justin Pryzby Discussion: https://postgr.es/m/20220731134135.GY15006@telsasoft.com Backpatch-through: 12 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/07abcd9ab712b843568e2f9a00006dd25797dc02 Modified Files -------------- src/bin/pg_upgrade/file.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone @ 2022-08-01 07:40 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 5+ messages in thread From: Michael Paquier @ 2022-08-01 07:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix error reporting after ioctl() call with pg_upgrade --clone errno was not reported correctly after attempting to clone a file, leading to incorrect error reports. While scanning through the code, I have not noticed any similar mistakes. Error introduced in 3a769d8. Author: Justin Pryzby Discussion: https://postgr.es/m/20220731134135.GY15006@telsasoft.com Backpatch-through: 12 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/8b1ec7d2953273501c5cea8185b6358dc7709eb5 Modified Files -------------- src/bin/pg_upgrade/file.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone @ 2022-08-01 07:40 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 5+ messages in thread From: Michael Paquier @ 2022-08-01 07:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Fix error reporting after ioctl() call with pg_upgrade --clone errno was not reported correctly after attempting to clone a file, leading to incorrect error reports. While scanning through the code, I have not noticed any similar mistakes. Error introduced in 3a769d8. Author: Justin Pryzby Discussion: https://postgr.es/m/20220731134135.GY15006@telsasoft.com Backpatch-through: 12 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/523926dea97f360f1f785853eea49e4dc4a6e1e9 Modified Files -------------- src/bin/pg_upgrade/file.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2022-08-01 07:40 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-08-01 07:40 pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone Michael Paquier <michael@paquier.xyz> 2022-08-01 07:40 pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone Michael Paquier <michael@paquier.xyz> 2022-08-01 07:40 pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone Michael Paquier <michael@paquier.xyz> 2022-08-01 07:40 pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone Michael Paquier <michael@paquier.xyz> 2022-08-01 07:40 pgsql: Fix error reporting after ioctl() call with pg_upgrade --clone Michael Paquier <michael@paquier.xyz>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox