[Pdns-dev] Sqlite3 locking

[Angelo Ativo]

Thank you for the response Justin, it’s much appreciated.

—Angelo


> On Sep 12, 2016, at 1:08 PM, Justin Clift <justin at postgresql.org> wrote:
> 
> On 12 Sep 2016, at 20:53, Angelo Ativo <aativo at threatstop.com> wrote:
> <snip>
>> Wouldn’t the chances of this failure be relatively high if there were say, hundreds of NSUPDATE requests to a PDNS server backed by sqlite3 every second? What happens when two NSUPDATE requests occur at the exact same time?
> 
> Note - I’m not a PDNS developer, so can’t comment on the retry thing (though
> it sounds useful).
> 
> Specifically with the SQLite bit though, it’s not really designed for high
> write rates (with contention).  If someone’s usage is becoming like that,
> it’d be a good idea to migrate the SQL backend to something  with good write
> contention handling. (there are many options, though naturally I’ll point
> at PostgreSQL as being decent :>)
> 
> Regards and best wishes,
> 
> Justin Clift
> 
> --
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
> - Indira Gandhi
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.powerdns.com/pipermail/pdns-dev/attachments/20160914/c556d3d2/attachment.sig>