Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
От | Alvaro Herrera |
---|---|
Тема | Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |
Дата | |
Msg-id | 1309460503-sup-6413@alvh.no-ip.org обсуждение исходный текст |
Ответы |
Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |
Список | pgsql-hackers |
Excerpts from Alvaro Herrera's message of jue jun 30 11:58:09 -0400 2011: > Enable CHECK constraints to be declared NOT VALID > > [...] > > This patch was sponsored by Enova Financial. Robert Hass (whose name I misspelled in the commit message above) just mentioned to me (in an answer to my apologizing about it) that he didn't think that mentioning sponsors for patch development was a good idea. I don't think we have a policy for this, but I have done it for some time now and nobody has complained, so I sort of assumed it was okay. Besides, some of the people pouring the money in does care about it; moreover, it provides a little incentive for other companies that might also be in a position to fund development but lack the "peer approval" of the idea, or a final little push. So what's the general opinion here? -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: