Timeline for PostgreSQL GIN pg_trgm default operator class
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2016 at 11:34 | comment | added | CarefreeSlacker | @jjanes I have been asked for developer. He said that there will be only two probably occasions: 1 -> If other extension will try to set default op class (more possible), then there will be error during adding extension. 2 -> If there will be default op class in postgres core (nearly impossible in near future) then pg_update will fail. | |
| Aug 8, 2016 at 17:18 | comment | added | jjanes | Upgrading postgres versions. Fortunately I think the problem is only with major version upgrades, not minor version upgrades. | |
| Aug 8, 2016 at 7:54 | comment | added | CarefreeSlacker | @jjanes The project is rather static. What do you mean when you say that i'am guarantee problems during migration of update. You re talking about adding new table or updating postgres version? | |
| Aug 4, 2016 at 6:03 | comment | added | cohenjo | It's a simple update to run with the extension creation, it's a small price to pay :) | |
| Aug 4, 2016 at 4:34 | comment | added | jjanes | @cohenjo Sure the DBA can micromanage the database, but isn't that directly at odds with what RoR is intended for? | |
| Aug 3, 2016 at 15:28 | comment | added | cohenjo | Postgres doesn't have a preference to what is the default behavior, it's up to the DBA to make sure which opclass is default. As with any upgrade/migration the DBA will need to make sure that this setting persists. | |
| Aug 3, 2016 at 15:10 | comment | added | jjanes | This works immediately, but is pretty dreadful. You are almost guaranteeing yourself problems when it comes to upgrading your database or merging two databases together into one, or splitting one apart. | |
| Aug 2, 2016 at 15:06 | vote | accept | CarefreeSlacker | ||
| Aug 2, 2016 at 12:37 | comment | added | András Váczi |
Let me add a small advisory: manually changing the system catalog may result in unexpected behaviour. This solution works until there is no conflict on the default operator class: if another extension would have its set to default for type text, this change would cause a conflict.
|
|
| Aug 2, 2016 at 10:46 | history | answered | cohenjo | CC BY-SA 3.0 |