[rttopo-dev] reserving face identifiers for state flags

[Sandro Santilli]

On Wed, Sep 14, 2016 at 03:04:06PM +0200, Sandro Santilli wrote:

> As a backend might refuse to allow a <side>_face value which does not
> exist in the <face> table, the library also creates a "placeholder"
> face there with the hard-coded identifier.  Shall the backend topology
> already have a face with the hard-coded value for "unassigned face",
> the backend would raise an exception there, making the process fail.

I'm witnessing a very long time spent by PostgreSQL processing
a DELETE, during a topology.RegisterMissingFaces call.
As the only expected DELETE is deletion of the placeholder
face, I'm now wondering if it makes sense to avoid using
the backend for state completely :(

It's hard to know what to expect by different backends, especially
as the library is not in charge of creating foreign keys and
the like on the actual tables...

--strk;