Em qua, 28 de nov de 2018 às 22:40, Justin Pryzby
escreveu:
> On Wed, Nov 28, 2018 at 05:03:15PM +1300, David Rowley wrote:
> > On Wed, 28 Nov 2018 at 03:16, Sanyo Moura wrote:
> > > 11.0
> > > Planning Time: 7.238 ms
> > > Planning Time: 2.638 ms
> > >
> > > 11.5
> > > Planning Time: 15138.533
On Wed, Nov 28, 2018 at 05:03:15PM +1300, David Rowley wrote:
> On Wed, 28 Nov 2018 at 03:16, Sanyo Moura wrote:
> > 11.0
> > Planning Time: 7.238 ms
> > Planning Time: 2.638 ms
> >
> > 11.5
> > Planning Time: 15138.533 ms
> > Execution Time: 2.310 ms
>
> Does it still take that long after runnin
On 11/28/18, 2:18 PM, "Justin Pryzby" wrote:
On Wed, Nov 28, 2018 at 07:08:53PM +, Scott Rankin wrote:
> We recently moved our production database systems from a 9.4 running on a
self-managed EC2 instance to 9.6.10 on Amazon’s AWS (same RAM, CPU). After the
move, we’re finding tha
On Wed, Nov 28, 2018 at 07:08:53PM +, Scott Rankin wrote:
> We recently moved our production database systems from a 9.4 running on a
> self-managed EC2 instance to 9.6.10 on Amazon’s AWS (same RAM, CPU). After
> the move, we’re finding that certain queries that we run against a GIN
> full-
Hello all,
We recently moved our production database systems from a 9.4 running on a
self-managed EC2 instance to 9.6.10 on Amazon’s AWS (same RAM, CPU). After the
move, we’re finding that certain queries that we run against a GIN full-text
index have some occasionally very slow executions and
