Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

18 postgres #183

Closed
RekGRpth opened this issue Jan 22, 2025 · 2 comments
Closed

18 postgres #183

RekGRpth opened this issue Jan 22, 2025 · 2 comments

Comments

@RekGRpth
Copy link

RekGRpth commented Jan 22, 2025 •
edited
Loading

How will you now save the original signal function to call it later, for 18 postgres, which has void pqsignal?

pgsql-http/http.c

Line 345 in 9ae0520

pgsql_interrupt_handler = pqsignal(SIGINT, http_interrupt_handler);

@pramsey
Copy link
Owner

pramsey commented Jan 22, 2025

Just ran into this in postgis too. Not sure.

@pramsey
Copy link
Owner

pramsey commented Jan 22, 2025

Some discussion about paths forward, looks doable.

https://www.postgresql.org/message-id/flat/4E796D56-79B5-4447-9DA7-5428BC1A6B53%40cleverelephant.ca

pramsey added a commit that referenced this issue Jan 22, 2025
@pramsey
Replace signal-based interrupt handling with a simple
17bd258 
glance at the PgSQL internal interrupt global state
values. References #183
pramsey added a commit that referenced this issue Jan 22, 2025
@pramsey
Replace signal-based interrupt handling with a simple
0895be5 
glance at the PgSQL internal interrupt global state
values. References #183
@pramsey pramsey closed this as completed Jan 23, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pramsey @RekGRpth