On Fri, Nov 22, 2024 at 6:57 AM wrote:
> Yeah, this is still on my list of things to research more about
> eventually - currently still unsolved.
>
> For my use-case the NO RESET would need to apply until the end of the
> transaction, not end of the session.
>
> I imagine something like an extens
On Wed, Nov 13, 2024 at 12:02 PM wrote:
> I don't have any benchmarks, but the following data point:
>
> We use PostgREST [1] which connects to the database with one
> "authenticator" role. For each request it handles, it does a SET ROLE to
> a role defined in the Authorization Header (JWT).
>
>
;t be installed in two
schemas at the same time. Which ever extension is installed first will
create the dep in the target schema, and then the second extension will try
to install the dep and fail due to it being already installed.
Thanks,
Eric
--
Eric Hanson
CEO, Aquameta Labs
503-929-1073
www.aquamet
a.
Is there a way to use CREATE EXTENSION ... CASCADE and specify in the
control file which schema the dependencies are installed in? How does the
extension know where to install its dependencies?
Thanks,
Eric
--
Eric Hanson
CEO, Aquameta Labs
503-929-1073
www.aquameta.com
--
-- Eric Hanso
;c.attnum = any(v.indkey)
> order by
>c.attnum asc;
>
> An other simpler case.
>
> select
>indexname
> from
>pg_catalog.pg_indexes
> where
>schemaname = 'act'
> and tablename = i_table_name
>and indexname = i_table_name || '_hist';
>
>
> --
> Öffentlicher PGP-Schlüssel:
> http://pgp.mit.edu/pks/lookup?op=get&search=0xCA167FB0E717AFFC
>
--
-- Eric Hanson CEO, Aquameta 503-929-1073
