Hi Tomas,
On Tue, 16 Nov 2021, at 22:03, Tomas Vondra wrote:
> It sure smells like a case of correlated data for some clients but not
> others, but who knows ... Hard to say without seeing the nodes below the
> join. If the lower nodes are estimated accurately, then it's the join
> selectivity
On 11/18/21 06:45, Dennis wrote:
Hi,
Are there any scripts that we can check after the changes we made in the
database code?
Who made what changes in what code?
In summary, are there any automatic post-development scripts before they
come to the beta stage?
Development of what and whose
Am Thu, Nov 18, 2021 at 05:45:37PM +0300 schrieb Dennis:
> Are there any scripts that we can check after the changes we made in the
> database code?
> In summary, are there any automatic post-development scripts before they
> come to the beta stage?
What do you want those script to do ?
Karsten
DAVID ROTH writes:
> The code I am migrating uses the EXECUTE immediate form for almost
> everything. The path of least resistance for me is to just copy the code to
> Postgres and change "EXECUTE IMMEDIATE" to "EXECUTE".
> I am asking about performance differences to see if it is worth
Hi, the case is:
one day we did full backup of database version 12 using standard procedure
of continuous backup so: pg_start_backup/rsync/pg_stop_backup
snip of WAL files archive directory:
ver 12 PG
Jul 28 04:37 000103340004
Jul 28 04:41 000103340005
Jul 28 05:16
Agreed.
The code I am migrating uses the EXECUTE immediate form for almost everything.
The path of least resistance for me is to just copy the code to Postgres and
change "EXECUTE IMMEDIATE" to "EXECUTE".
I am asking about performance differences to see if it is worth converting code
that does
Hi,
Are there any scripts that we can check after the changes we made in the
database code?
In summary, are there any automatic post-development scripts before they
come to the beta stage?
Dennis
DAVID ROTH schrieb am 18.11.2021 um 15:15:
> I am working on a large Oracle to Postgres migration.
> The existing code frequently constructs a string and then uses Oracle's
> "EXECUTE IMMEDIATE" to run it.
> "EXECUTE" has the same functionality in Postgres.
>
> For example:
> CREATE or REPLACE
I am working on a large Oracle to Postgres migration.
The existing code frequently constructs a string and then uses Oracle's
"EXECUTE IMMEDIATE" to run it.
"EXECUTE" has the same functionality in Postgres.
For example:
CREATE or REPLACE FUNCTION djr_foo_fnc (p_emp_no IN number)
RETURN VARCHAR2
čt 18. 11. 2021 v 12:24 odesílatel Abdul Mohammed
napsal:
> Hello everyone,
> Please I am having a problem with a function I am writing. The first part
> uses a loop that pulls the values from a column and concatenates them into
> a string. This first part works fine. The second part tries to
Hello everyone,
Please I am having a problem with a function I am writing. The first part
uses a loop that pulls the values from a column and concatenates them into
a string. This first part works fine. The second part tries to use the
string to build a pivot table using the crosstab function. The
11 matches
Mail list logo
