Decibel! wrote:
>
>
> Yes, but that provides no help at all outside of pg_dump. Being able
> to add a FK with NO CHECK would be tremendously useful outside of
> pg_dump. Actually, in the interest of stating the problem and not the
> solution, what we need is a way to add FKs that doesn't lock
> everything up to perform the key checks. Perhaps there is some
> semi-safe way that the constraint could be added and the checks done
> in the background...
I had some thoughts along the same lines.
But how do you propose to recover when the check fails? What should
pg_restore do if the dump is corrupt causing an FK check to fail?
I suppose we could have some sort of marking for FK constraints along
the lines of {checked, unchecked, invalid}.
>
> As for the footgun aspect, are we the enterprise-class OSS database or
> the one that caters itself to noobs that will go out of their way to
> make life hard on themselves?
We are the database that tries very hard to keep its promises. If you
want to change or relax those promises then the implications need to be
very very clear.
> I'm all in favor of not adding footguns that don't have value, but
> this one holds a lot of value for anyone trying to maintain a large
> database in a 24/7 environment. To put this in perspective, the amount
> of revenue we would loose from adding just one FK to one of our larger
> tables would more than cover paying someone to develop this feature.
>
Come up with a good proposal and I'm your man :-) I haven't seen one yet.
cheers
andrew
