Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Force core dump creation and dump stack traces of all threads if a test times out #60

Closed
mbautin opened this issue Feb 24, 2018 · 1 comment
Assignees

Comments

@mbautin
Copy link
Contributor

mbautin commented Feb 24, 2018

No description provided.

@mbautin mbautin self-assigned this Feb 24, 2018
mbautin pushed a commit that referenced this issue Jun 20, 2019
Not put underline for links inside a data table
@bmatican
Copy link
Contributor

bmatican commented Mar 3, 2022

Closing as we have several attempts to signal to shutdown, on test timeout, including SIGSEGV

@bmatican bmatican closed this as completed Mar 3, 2022
tvesely pushed a commit to tvesely/yugabyte-db that referenced this issue Feb 28, 2024
This commit fixes and extends the extension SQL scripts in a few ways,
to allow upgrades from all the possible versions down where the origin
is based on PostgreSQL 10, which is the oldest version supported by
pg_hint_plan currently.

PostgreSQL allows since v10 the maintenance of an extension using as
base script the oldest version supported in combination of incremental
scripts.  A full set of upgrade scripts is added by this commit,
considering v10 as the oldest path supported.  As origin versions
may have a partial schema created for the hint table with partial
definitions, the correct rules are enforced for each version when it
comes to extension dumps and GRANT rules.  The schema for the hint table
is only created in the base script.

Regression tests are added to cover all these upgrade paths.  DATA in
the Makefile is changed to hardcode all the SQL scripts that need to be
installed.

Per pull request yugabyte#111 and issues yugabyte#110 and yugabyte#60.

Backpatch-through: 10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants