evergreen.change_db_setting needs test
Bug #1483496 reported by
Liam Whalen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Test Writing Day - 2015/08/14
This is a potential target for a pgTap test.
| tags: | added: test-writing-day-0 |
| Changed in evergreen: | |
| assignee: | nobody → Josh Stompro (u-launchpad-stompro-org) |
Revision history for this message
| Josh Stompro (u-launchpad-stompro-org) wrote | #1 |
| Changed in evergreen: | |
| assignee: | Josh Stompro (u-launchpad-stompro-org) → nobody |
| tags: | removed: test-writing-day-0 |
| tags: | added: needstest |
Revision history for this message
| Galen Charlton (gmc) wrote | #2 |
| Changed in evergreen: | |
| status: | New → Won't Fix |
To post a comment you must log in.
I cannot figure out a way to test this. change_db_setting is a wrapper around alter database, but the results of that command only take effect for new connections. The current session doesn't know about the change. So there is no way to that I can see to begin a transaction, alter a database runtime setting, confirm that it was changed, and rollback the transaction.
Maybe someone else can figure it out.
This is a core postgresql feature though, setting the schema search path, and using alter database.
Josh