Modify ↓
Opened 14 years ago
Last modified 9 years ago
#9399 new defect
Specify tablespace when connecting to postgresql
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | unscheduled |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | bitesized, postgresql |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
In our postgres setup we have multiple tablespaces. Trac should be using its own, but the default is incorrect. There should be a way to specify the default tablespace in the connection settings, like we can specify schema. This is a nasty problem when plugins attempt to create tables, or when the DB needs to be upgraded.
Attachments (0)
Change History (3)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Keywords: | bitesized added |
|---|---|
| Milestone: | → unscheduled |
Sounds like a relatively easy task. Patch welcome.
comment:3 by , 9 years ago
| Keywords: | postgresql added; postgres removed |
|---|
Note:
See TracTickets
for help on using tickets.
Sorry, hit submit accidentally.
Trac is attempting to use the wrong tablespace, but failing. As a result it can't create or modify any tables. I'm changing the default on the server, but that's a bit of a problem for other reasons. If I could just specify the default tablespace to use in the connection string, like you do with schema, I could set it to whatever I needed explicitly and bypass the whole issue.