The language used for stored procedures is EDBSPL. Even if we dont use
EDBSPL, and instead use PLPgPSQL, the performance is still the same.
Thanks
On 24 October 2017 at 03:29, Steve Atkins wrote:
>
> > On Oct 23, 2017, at 12:19 PM, Purav Chovatia wrote:
> >
> > Hello Experts,
> >
> > We are tr
Hi Pascal,
Do you mean the sample program that acts as the application, do you want me
to share that? I can do that, but I guess my post will get blocked.
Yes, c1 is the PK. Pls see below:
bmdb=# desc dept_new
Table "public.dept_new"
Column | Type | Modifiers
+
Hi Pavel, *,
you were right with ANALYZing the DB first. However, even after doing
so, I frequently see Seq Scans where an index was used before. This
usually cooccurs with parallelization and looked different before
upgrading to 10. I can provide an example for 10 [1], but I cannot
generate a que
Please share how you monitor your perfs.
At less duration for each plpgsql proc / oracle proc.
Please share your plpgsql code, and commit strategy.
(for support with edb please check with your contract manager)
--
Sent from:
http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.ht
We record like this: perf record -g -u enterprisedb
We report like this: perf report -g -i perf.data
Is this what you were looking for? Sorry, we are new to perf so we might be
sharing something different as compared to what you asked.
We already shared the SP code in the original post.
Thanks
On Tue, Oct 24, 2017 at 04:15:59PM +0200, johannes graën wrote:
> upgrading to 10. I can provide an example for 10 [1], but I cannot
> generate a query plan for 9.6 anymore.
You could (re)install PG96 alongside PG10 and run a copy of the DB (even from
your homedir, or on a difference server) and p
Once again you are speaking about edb port of postgresql. The edb pl sql code
is not public. This is not the good place to get support: please ask your
edb contract manager.
If you want support hère: please rewrite your oracle proc in pl pqsql, share
that code and commit strategy ... Postgres doesn
On 2017-10-24 17:18, Justin Pryzby wrote:
> You could (re)install PG96 alongside PG10 and run a copy of the DB (even from
> your homedir, or on a difference server) and pg_dump |pg_restore the relevant
> tables (just be sure to specify the alternate host/port/user/etc as needed for
> the restore in
johannes graën wrote:
> Hi Pavel, *,
>
> you were right with ANALYZing the DB first. However, even after doing
> so, I frequently see Seq Scans where an index was used before. This
> usually cooccurs with parallelization and looked different before
> upgrading to 10. I can provide an example for 1
