S
slacroixak
Guest
Thank you for all your posts Sirs. I understand very well that in case of opened transactions it is expected to take time to shut down a DB. However, in my tests, I just do not start any transaction, and I even play with one single User. To tell you all, I am working at solving an old interesting problem : our App works with a main DB, and an additional DB rather rarely. Until now, for this 2nd DB, our guys used to apply the following pattern ; 1-connect, 2-do-something 3-disconnect. I'd like to stop that and keep long term connections for performance sake (let alone the log file), but some like the ability to be able to shut down that additional DB without causing error 778 and 735 (error reading socket etc...) in the client sessions when it is not used, which I like the idea. => don't make me wrong, for the main DB with long term DB bound code, I know very well there is no way to do that and it is fine. Now, it seems that I have found a reliable way to catch and handle these errors 778 and 735 as long as we keep the connection quite (not DB bound .r code kept in memory, nor any dynamic buffer, and of course no transaction). As I am testing this, I need to often stop and restart this local 2nd DB of mine, a DB that has a very tiny activity (just one single quick read), then I started to wonder whether it would it be possible to reduce these long 30s for a simple shutdown Could it be faster if I start the DB with a small value for some parameters ? (-L -B etc...) TIA
Continue reading...
Continue reading...