What problem are you trying to solve?
It would be very helpfull for postgress backend users to have a way to specify a table is unlogged.
Proposed solution
model MyPubSubQueue {
...
@@unlogged
}Alternatives considered
Currently this requires, and is widely recommended for, manually updating migration files.
Scope and impact
Zero impact.
Anyone with the previous manual migrations might get a zero-side-effect alter table migration if they opt to start adding the new annotation to their existing tables.
Downside might be having to document in backends where this feature is not available (and point out where they are always-on at backends that only have ephemeral memory storage?)
What problem are you trying to solve?
It would be very helpfull for postgress backend users to have a way to specify a table is unlogged.
Proposed solution
Alternatives considered
Currently this requires, and is widely recommended for, manually updating migration files.
Scope and impact
Zero impact.
Anyone with the previous manual migrations might get a zero-side-effect alter table migration if they opt to start adding the new annotation to their existing tables.
Downside might be having to document in backends where this feature is not available (and point out where they are always-on at backends that only have ephemeral memory storage?)