so 2. 1. 2021 v 21:02 odesílatel Joel Jacobson napsal:
> 13.1
>
ok there is plpgsql most fast
you can check if there are not some hidden implicit casting in your code.
Regards
Pavel
> On Sat, Jan 2, 2021, at 20:37, Pavel Stehule wrote:
>
> Hi
>
> so 2. 1. 2021 v 20:07 odesílatel Joel Jacobs
13.1
On Sat, Jan 2, 2021, at 20:37, Pavel Stehule wrote:
> Hi
>
> so 2. 1. 2021 v 20:07 odesílatel Joel Jacobson napsal:
>> __
>> I found yet another trick, which actually seems to be slightly faster than
>> the plpgsql version.
>
> What version of Postgres do you use?
>
> plpgsql in Postgres
Hi
so 2. 1. 2021 v 20:07 odesílatel Joel Jacobson napsal:
> I found yet another trick, which actually seems to be slightly faster than
> the plpgsql version.
>
What version of Postgres do you use?
plpgsql in Postgres 13 is significantly faster than on older versions
Regards
Pavel
> The tri
I found yet another trick, which actually seems to be slightly faster than the
plpgsql version.
The trick is to use VIEW ... WITH (security_barrier) to tell the optimizer it
shouldn’t flatten the subqueries.
CREATE TABLE eastern (year integer);
INSERT INTO eastern (year) SELECT generate_series
On 1/2/21 2:23 AM, Dirk Mika wrote:
In particular, columns are populated with values if they are not specified in
the update statement which is used.
Usually with an expression like this:
IF NOT UPDATING('IS_CANCELED')
THEN
:new.is_canceled := ...;
END IF;
I have not
On Sat, Jan 2, 2021 at 12:50 PM robert wrote:
>
> Friends
>
> I hope you had a good start into 2021.
>
>
> I would like to get some advice on how to restore a 9.1 DB, of which I have
> the
>
> /var/lib/postgresql
>
> with some 20GB salvaged.
>
> Now I find now easily usable 9.1 PostgreSQL install
Friends
I hope you had a good start into 2021.
I would like to get some advice on how to restore a 9.1 DB, of which I have the
/var/lib/postgresql
with some 20GB salvaged.
Now I find now easily usable 9.1 PostgreSQL installer anymore.
How should I proceed to get that data in a newer PG load
> On 1 Jan 2021, at 16:56, Dirk Mika wrote:
>
> Hi all and a happy new Year!
>
> We have an Oracle schema that is to be converted to PostgreSQL, where
> conditional predicates are used in some triggers.
>
> In particular, columns are populated with values if they are not specified in
> the
> > In particular, columns are populated with values if they are not specified
> > in the update statement which is used.
> > Usually with an expression like this:
> >
> > IF NOT UPDATING('IS_CANCELED')
> > THEN
> > :new.is_canceled := ...;
> > END IF;
> >
> > I have not fou
> > PostgreSQL doesn't have an exact equivalent. Typically, the OLD and NEW
> > values are compared and then action is taken based on that. For example,
> > in PL/pgSQL:
> > IF NEW.is_canceled IS NOT DISTINCT FROM OLD.is_canceled THEN
> > NEW.is_canceled := etc etc ;
> > ENDIF;
> > There's cur
10 matches
Mail list logo
