Timeline for PostgreSQL: Add or drop column under load give wrong number of columns errors
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2017 at 11:43 | comment | added | viblo | Discussion from pgsql-general mailing list: postgresql.org/message-id/flat/… | |
| Mar 8, 2017 at 9:50 | answer | added | Dave Poole | timeline score: 1 | |
| Nov 3, 2015 at 6:26 | history | edited | viblo | CC BY-SA 3.0 |
Added full steps to recreate the error
|
| Oct 10, 2015 at 3:36 | comment | added | viblo | I did a report on the pgsql-general mailing list, but so far no solution. | |
| Oct 9, 2015 at 16:47 | history | tweeted | twitter.com/StackDBAs/status/652525842409615361 | ||
| Oct 9, 2015 at 14:53 | comment | added | Erwin Brandstetter |
ALTER TABLE takes an ACCESS EXCLUSIVE lock on the table (at least it's supposed to). It may be hard to ensure that the row type to go with the table is not in use either, especially by prepared statements (and plpgsql functions, maybe others too) - or maybe it's an oversight, i.e. a bug ...
|
|
| Oct 9, 2015 at 6:07 | comment | added | Craig Ringer | Relevant mailing list post: postgresql.org/message-id/[email protected] . It's old, not sure if any improvements were made since then. You might have more luck following up on pgsql-general or raising a bug on pgsql-bugs. | |
| Oct 9, 2015 at 5:57 | history | edited | viblo | CC BY-SA 3.0 |
edited title
|
| Oct 9, 2015 at 5:07 | history | asked | viblo | CC BY-SA 3.0 |