Re: Crippling query plan change between 3.7.13 and 3.8.10.2

2015-05-28 Thread Florian Weimer
* Florian Weimer: I will figure out a way to rewrite the query so that it runs reasonably fast again (which will address our immediate needs), but maybe there is something that can be fixed in the planner as well. I committed something and restarted the daemon. The page still loads extremely

Re: [sqlite] Crippling query plan change between 3.7.13 and 3.8.10.2

2015-05-28 Thread Richard Hipp
On 5/28/15, Florian Weimer f...@deneb.enyo.de wrote: The Debian security tracker https://security-tracker.debian.org/ uses an SQLite database to keep track of vulnerabilites and generate reports. We recently upgraded SQLite from 3.7.13 to 3.8.7.1 as part of an operating system upgrade and

Re: upgrading soler.d.o

2015-05-28 Thread Florian Weimer
* Salvatore Bonaccorso: If one tries to access the JSON format url this triggers the issue. Thanks for isolating the issue and providing a test case. I can reproduce locally. It may not be a memory leak, but a change in the SQLite query planner. The problematic query appears to be: SELECT

Crippling query plan change between 3.7.13 and 3.8.10.2

2015-05-28 Thread Florian Weimer
The Debian security tracker https://security-tracker.debian.org/ uses an SQLite database to keep track of vulnerabilites and generate reports. We recently upgraded SQLite from 3.7.13 to 3.8.7.1 as part of an operating system upgrade and experienced a crippling query planner change. I verified

Re: [sqlite] Crippling query plan change between 3.7.13 and 3.8.10.2

2015-05-28 Thread Richard Hipp
On 5/28/15, Richard Hipp d...@sqlite.org wrote: In the meantime, you can work around the problem by manifesting the view yourself. Another temporary work-around is to run the following C-langauge API when the process first starts up (or at any other time prior to running the query that is not

Re: [SECURITY] [DSA 3269-1] postgresql-9.* security update

2015-05-28 Thread Salvatore Bonaccorso
Hi, On Thu, May 28, 2015 at 12:50:43PM +0200, ma...@wk3.org wrote: Hi, it seems this upgrade introduced some issues regarding symlinks. It's very easy to mitigate, but I guess less stressful if you know about it in advance:

Re: upgrading soler.d.o

2015-05-28 Thread Salvatore Bonaccorso
Hi. On Thu, May 28, 2015 at 06:34:44AM +0200, Salvatore Bonaccorso wrote: Hi, On Thu, May 28, 2015 at 11:39:34AM +0800, Paul Wise wrote: On Wed, 2015-05-27 at 22:16 +0200, Salvatore Bonaccorso wrote: It was updated already and did afterwards some testing. Looks fine so far. The

Re: [SECURITY] [DSA 3269-1] postgresql-9.* security update

2015-05-28 Thread ma...@wk3.org
Hi, it seems this upgrade introduced some issues regarding symlinks. It's very easy to mitigate, but I guess less stressful if you know about it in advance: https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug Sincerely, Malte -- To UNSUBSCRIBE, email to

Re: upgrading soler.d.o

2015-05-28 Thread Salvatore Bonaccorso
Hi all, On Thu, May 28, 2015 at 10:33:19AM +0200, Salvatore Bonaccorso wrote: Hi. On Thu, May 28, 2015 at 06:34:44AM +0200, Salvatore Bonaccorso wrote: Hi, On Thu, May 28, 2015 at 11:39:34AM +0800, Paul Wise wrote: On Wed, 2015-05-27 at 22:16 +0200, Salvatore Bonaccorso wrote: