Log Message: ----------- Fix DROP RESOURCE QUEUE so that it destroys the in memory queue along with the catalog queue object. This does mean that it is possible to have foot gun moments via ALTER ROLE ... RESOURCE QUEUE <none> for a connected user and then DROP RESOURCE QUEUE on the role's queue. However this is no worse IMHO than being able to do DROP ROLE on a role that is correctly connected! Modified Files: -------------- bizgres/postgresql/src/backend/utils/resscheduler: resqueue.c (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/resqueue.c.diff?r1=1.7&r2=1.8) resscheduler.c (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/resscheduler.c.diff?r1=1.6&r2=1.7) bizgres/postgresql/src/include/utils: resscheduler.h (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/utils/resscheduler.h.diff?r1=1.6&r2=1.7)
pgsql-committers by date:
Соглашаюсь с условиями обработки персональных данных