plsqlvids01 plsqlvids01 writes:
> AWS RDS Postgres database on v12.17 is upgraded to v16.1, as per
> https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-extensions.html#postgresql-extensions-16x
> am
> trying to upgrade pg_cron and pgaudit extensions
On 2024-Aug-21, plsqlvids01 plsqlvids01 wrote:
> AWS RDS Postgres database on v12.17 is upgraded to v16.1, as per
> https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-extensions.html#postgresql-extensions-16x
> am
> trying to upgrade pg_cron and pgaudit ex
On 8/21/24 12:14, plsqlvids01 plsqlvids01 wrote:
AWS RDS Postgres database on v12.17 is upgraded to v16.1, as per
https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-extensions.html#postgresql-extensions-16x <https://docs.aws.amazon.com/AmazonRDS/lat
AWS RDS Postgres database on v12.17 is upgraded to v16.1, as per
https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-extensions.html#postgresql-extensions-16x
am
trying to upgrade pg_cron and pgaudit extensions but it keeps throwing the
same error, how to upgrade them
On Wednesday, June 19, 2024, Ayush Vatsa wrote:
> Hi David,
> Thanks for clarification
> > I prefer TABLE. Using setof is more useful when the returned type is
> predefined
> But in the table also isn't the returned type predefined? Example:
> CREATE FUNCTION fun1(integer)
> RETURNS TABLE(
>
Hi David,
Thanks for clarification
> I prefer TABLE. Using setof is more useful when the returned type is
predefined
But in the table also isn't the returned type predefined? Example:
CREATE FUNCTION fun1(integer)
RETURNS TABLE(
col1 integer,
col2 text
)
AS 'MODULE_PATHNAME', 'fun1
"David G. Johnston" writes:
> On Tuesday, June 18, 2024, Ron Johnson wrote:
>> What's the purpose? Legacy of not having procedures?
> So people can have a style guide that says always specify a returns clause
> on function definitions.
To my mind, the reason we allow RETURNS together with OUT
On Tuesday, June 18, 2024, Ron Johnson wrote:
> On Tue, Jun 18, 2024 at 2:37 PM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Tuesday, June 18, 2024, Ron Johnson wrote:
>>
>>> On Tue, Jun 18, 2024 at 1:57 PM David G. Johnston <
>>> david.g.johns...@gmail.com> wrote:
>>>
O
On Tue, Jun 18, 2024 at 2:37 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Tuesday, June 18, 2024, Ron Johnson wrote:
>
>> On Tue, Jun 18, 2024 at 1:57 PM David G. Johnston <
>> david.g.johns...@gmail.com> wrote:
>>
>>> On Tuesday, June 18, 2024, Ron Johnson wrote:
>>>
On Tuesday, June 18, 2024, Ron Johnson wrote:
> On Tue, Jun 18, 2024 at 1:57 PM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Tuesday, June 18, 2024, Ron Johnson wrote:
>>
>>>
>>> But I stand by returning OUT params and records at the same time.
>>>
>>
>> You mean you dislike
On Tue, Jun 18, 2024 at 1:57 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Tuesday, June 18, 2024, Ron Johnson wrote:
>
>>
>> But I stand by returning OUT params and records at the same time.
>>
>
> You mean you dislike adding the optional returns clause when output
> parameters
On Tuesday, June 18, 2024, Ron Johnson wrote:
>
> But I stand by returning OUT params and records at the same time.
>
You mean you dislike adding the optional returns clause when output
parameters exist? Because the out parameters and the “record” represent
the exact same thing.
David J.
On Tue, Jun 18, 2024 at 1:16 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Tue, Jun 18, 2024 at 10:07 AM Ron Johnson
> wrote:
>
>> fun2 puzzles me. Why would you return parameters AND *a single record*
>> (unless
>> it's an error status).
>>
>
> You mis-understand what 2 is doi
On Tue, Jun 18, 2024 at 10:07 AM Ron Johnson
wrote:
> fun2 puzzles me. Why would you return parameters AND *a single record*
> (unless
> it's an error status).
>
You mis-understand what 2 is doing. You should go re-read the docs for
create function again. Especially the description of rettyp
On Tue, Jun 18, 2024 at 9:50 AM Ayush Vatsa
wrote:
> 1/ I wanted to know what's the difference between the above three
> definitions.
> As per my understanding, "fun1" and "fun2" look the same, taking one
> integer and returning two columns with multiple rows.
>
Yes.
>
> Can the above definiti
ve made my Comp
Sci professors very, very angry. Definitely Bad Practice.
You choose which to use based on how much data you want to return.
On Tue, Jun 18, 2024 at 12:50 PM Ayush Vatsa
wrote:
> Hi PostgreSQL community,
> Recently I am exploring extensions in postgres and got a little conf
Hi PostgreSQL community,
Recently I am exploring extensions in postgres and got a little confused
regarding the function definition present in SQL file. For example consider
below three functions:
CREATE FUNCTION fun1(integer)
RETURNS TABLE(
col1 integer,
col2 text
)
AS
Hi all,
I built a cookiecutter template for Postgres extensions.
This cookiecutter prompts for some basic extension metadata (e.g., name,
Postgres version) and then automatically generates the necessary boilerplate
files.
These include:
* Standard extension files (Makefile, .control, c
Switchover will be successful but new primary node will
> fail at startup process because shared_preload_libraries is empty but
> extensions are created in database? Or it's better to pre-configure same
> extensions into shared_preload_libraries parameter on replication server?
Having some
Dear all,
I have question regarding how extensions acting during switchover process.
We running PostgreSQL 11 HA primary/replication server that is configured
with repmgr.
Everything works fine but I am interested in matter of how extensions works
during failover/switchover.process.
Let'
On Tue, May 4, 2021 at 10:04 PM Ian Lawrence Barwick
wrote:
> 2021年5月5日(水) 10:43 Tiffany Thang :
> >
> > Hi,
> >
> > I'm having trouble finding in the documentation the steps to install the
> postgres extensions such as pg_stat_statements and pg_trgm on
&
2021年5月5日(水) 10:43 Tiffany Thang :
>
> Hi,
>
> I'm having trouble finding in the documentation the steps to install the
> postgres extensions such as pg_stat_statements and pg_trgm on PG13.1/CentOS7.
> Can someone please assist?
>
>
> postgres=# create extensi
Hi,
I'm having trouble finding in the documentation the steps to install the
postgres extensions such as pg_stat_statements and pg_trgm on
PG13.1/CentOS7. Can someone please assist?
postgres=# create extension pg_stat_statements;
ERROR: could not open extension control file
"/us
David,
Thank you -- that is exactly what I needed!
On Fri, Feb 26, 2021 at 2:06 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Fri, Feb 26, 2021 at 12:01 PM Adrian Klaver
> wrote:
>
>> Which refers to COPYRIGHT:
>>
>>
>> https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob
On Fri, Feb 26, 2021 at 12:01 PM Adrian Klaver
wrote:
> Which refers to COPYRIGHT:
>
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=COPYRIGHT;h=655a3c59d60f54a824cc8ad6c94a4522f2b465cd;hb=HEAD
>
>
The COPYRIGHT file indeed is serving as the in-repo documentation of our
license.
GHT;h=655a3c59d60f54a824cc8ad6c94a4522f2b465cd;hb=HEAD
Best Regards,
Rumpi
On Thu, Feb 25, 2021 at 6:26 PM Tom Lane <mailto:t...@sss.pgh.pa.us>> wrote:
Rumpi Gravenstein mailto:rgrav...@gmail.com>>
writes:
> I am new to PostgreSQL and am unclear on how licensing works for
PostgreSQL
On 2/26/21 11:39 AM, Rumpi Gravenstein wrote:
Tom
Thanks for the quick reply. What you stated is what I was expecting.
I've searched high and low for the documentation that proves that point
-- something I need to do to satisfy our legal team. Any thoughts on
under which rock that license
, Feb 25, 2021 at 6:26 PM Tom Lane wrote:
> Rumpi Gravenstein writes:
> > I am new to PostgreSQL and am unclear on how licensing works for
> PostgreSQL
> > extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
> > community edition or do PostgreSQL ext
Rumpi Gravenstein writes:
> I am new to PostgreSQL and am unclear on how licensing works for PostgreSQL
> extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
> community edition or do PostgreSQL extensions fall under a separate
> license? I've looked for docu
All,
Postgres 13.1
I am new to PostgreSQL and am unclear on how licensing works for PostgreSQL
extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
community edition or do PostgreSQL extensions fall under a separate
license? I've looked for documentation on this and ha
On Wed, 2020-11-18 at 14:46 +0100, Eric Svenson wrote:
> I am not really sure if I am in the right mailing list, but I try it here
> first.
>
> I have written a postgres C extension as DLL which was used with Postgres 9.2
> successfully.
>
> Now I am trying to upgrade to Postgres 13 but I ran i
Hello,
I am not really sure if I am in the right mailing list, but I try it here
first.
I have written a postgres C extension as DLL which was used with Postgres
9.2 successfully.
Now I am trying to upgrade to Postgres 13 but I ran into a compile problem.
The function
PG_GETARG_BYTEA_P
causes
On Sat, Sep 26, 2020 at 10:11 PM Tom Lane wrote:
>
> Julien Rouhaud writes:
> > So, apparently pg_available_extension_versions already had those
> > fields so all the required infrastructure was already there. I just
> > added the exact same fields to pg_available_extensions, see attached
> > pa
Julien Rouhaud writes:
> So, apparently pg_available_extension_versions already had those
> fields so all the required infrastructure was already there. I just
> added the exact same fields to pg_available_extensions, see attached
> patch.
The reason that pg_available_extensions has only the fie
On Fri, Sep 25, 2020 at 2:51 PM Daniel Westermann (DWE)
wrote:
>
> On Thu, Sep 24, 2020 at 10:58 AM Michael Paquier wrote:
> >>
> >> On Wed, Sep 23, 2020 at 03:28:45PM +, Daniel Westermann (DWE) wrote:
> >> > I was playing a bit with trusted extensio
On Thu, Sep 24, 2020 at 10:58 AM Michael Paquier wrote:
>>
>> On Wed, Sep 23, 2020 at 03:28:45PM +, Daniel Westermann (DWE) wrote:
>> > I was playing a bit with trusted extensions and wondered if there is
>> > a reason that the "trusted" flag is not ex
On Thu, Sep 24, 2020 at 10:58 AM Michael Paquier wrote:
>
> On Wed, Sep 23, 2020 at 03:28:45PM +, Daniel Westermann (DWE) wrote:
> > I was playing a bit with trusted extensions and wondered if there is
> > a reason that the "trusted" flag is not exposed in pg
On Wed, Sep 23, 2020 at 03:28:45PM +, Daniel Westermann (DWE) wrote:
> I was playing a bit with trusted extensions and wondered if there is
> a reason that the "trusted" flag is not exposed in pg_available_extensions.
> I believe that information would be quite usefu
Hi,
I was playing a bit with trusted extensions and wondered if there is a reason
that the "trusted" flag is not exposed in pg_available_extensions.
I believe that information would be quite useful so one can easily identify
extensions that can be installed as "normal" user.
Regards
Daniel
On Thu, Jun 18, 2020 at 02:26:04PM +, Winfield, Steven wrote:
> Many thanks for the pointers - I've submitted a patch.
Thanks Steve, I have noticed the patch. For the sake of the archives,
it is here:
https://www.postgresql.org/message-id/AM5PR0901MB1587E47B1ACF23C6089DFCA3FD9B0%40AM5PR0901MB
> This would not be a complicated change as it requires creating a new
> version script for those modules. You can look at commit 20eb273 as
> an example, and the work is even simpler now that we just need update
> scripts when bumping a module's version (those named foo--1.0--1.1.sql
> and not fo
On Wed, Jun 10, 2020 at 12:40:54PM -0400, Tom Lane wrote:
> "Winfield, Steven" writes:
>> There was a thread about this back in 2016[1], but I've just been
>> bitten by it and wondered if any (more) extensions, particularly
>> btree_gist, will have their operat
"Winfield, Steven" writes:
> There was a thread about this back in 2016[1], but I've just been bitten by
> it and wondered if any (more) extensions, particularly btree_gist, will have
> their operators/functions verified and marked as parallel-safe?
Whenever somebody do
Hi all,
There was a thread about this back in 2016[1], but I've just been bitten by it
and wondered if any (more) extensions, particularly btree_gist, will have their
operators/functions verified and marked as parallel-safe?
In our case, we're interested in the float8 <->
On Tue, 2020-02-18 at 15:06 -0500, Stephen Frost wrote:
>
> Policies, also being part of the overall privilege system, could
> certainly be looked at in a similar light as being different from
> triggers and indexes...
While I think I agree with Stephen here, I don't have a vested interest
in an
he extension's
objects.
While it's not as nice a solution at the pg_init_privs system, I would
be inclined to state explicitly (and perhaps even enforce) that enabling
RLS or creating policies as part of an extension isn't supported, and
then modify pg_dump to always dump out those
e
applies.
My use case is a tool that determines the state of a database for
performing diffs, etc. It can generate ddl from database diffs to
create or alter tables, etc, and can also deal with policies and
extensions but will not be able to deal with policies created in
extensions, which is d
Marc Munro writes:
> On Mon, 2020-02-17 at 22:48 -0500, Tom Lane wrote:
>> An RLS policy is a table "subsidiary object" so it only depends indirectly
>> on the extension that owns the table.
> Yep, I get that, and I see the dependency chain in the catalog.
> However an extension can create the
Marc Munro writes:
> I tried to define a policy within an extension but the policy does not
> seem to belong to the extension. Is this the way it is supposed to be?
Yeah, I would expect that.
https://www.postgresql.org/docs/current/extend-extensions.html
says:
The kinds of SQL objects tha
On 2/17/20 2:46 PM, Marc Munro wrote:
I tried to define a policy within an extension but the policy does not
seem to belong to the extension. Is this the way it is supposed to be?
This is postgres 9.5.21
Here is the relevant code from the extension:
create table rls2 (
username te
I tried to define a policy within an extension but the policy does not
seem to belong to the extension. Is this the way it is supposed to be?
This is postgres 9.5.21
Here is the relevant code from the extension:
create table rls2 (
username text not null,
details text not null
It works.
Thank you, thank you, thank you.
-- Original Message --
From: "Julien Rouhaud"
To: "Sterpu Victor"
Cc: pgsql-gene...@postgresql.org
Sent: 2020-02-13 3:48:08 PM
Subject: Re: Enabling extensions on a compiled instance of postgresql
12.1
On Thu, Feb 13
On Thu, Feb 13, 2020 at 01:34:55PM +, Sterpu Victor wrote:
> Hello
>
> I compiled from source postgresql 12.1 and all went fine but when I try to
> restore my DB I can see that I have 3 extensions missing: uuid-ossp,
> btree_gist, tablefunc.
> I tried to run: CREATE EXTENSIO
Hello
I compiled from source postgresql 12.1 and all went fine but when I try
to restore my DB I can see that I have 3 extensions missing: uuid-ossp,
btree_gist, tablefunc.
I tried to run: CREATE EXTENSION "uuid-ossp"; and the error is ERROR:
could not open extension control f
en extension
> on windows. Do you have an idea ?
>
> I don't do Windows myself but this blog from Craig Ringer looks like a
> good starting point:
>
>
> https://www.2ndquadrant.com/en/blog/compiling-postgresql-extensions-visual-studio-windows/
>
Regards Niels
-Oprindelig meddelelse-
Fra: Thomas Munro
Sendt: 7. januar 2020 21:56
Til: İlyas Derse
Cc: pgsql-generallists.postgresql.org
Emne: Re: Writing Postgres Extensions in C on Windows
On Wed, Jan 8, 2020 at 4:32 AM İlyas Derse wrote:
> I want to register C code to Postgre
m Craig Ringer looks like a
good starting point:
https://www.2ndquadrant.com/en/blog/compiling-postgresql-extensions-visual-studio-windows/
I want to register C code to PostgreSql on Windows. So I think, I have to
make a extension for PostgreSql. But I did not find to written extension on
windows. Do you have an idea ?
Thanks ...
> From: Morris de Oryx
>
> Not sure about best practices, but what I'm going is like this:
>
> * Create a schema named extensions.
> * Install extensions in this special schema only. I don't put anything else
> in there.
> * Put the extensions schema early (left
Not sure about best practices, but what I'm going is like this:
* Create a schema named extensions.
* Install extensions in this special schema only. I don't put anything else
in there.
* Put the extensions schema early (left) in the search_path for each role.
* Grant exec
ruser it shows up in the \dx display
>
>> BUT as a normal user:
>
>> stan=> \dx
>> List of installed extensions
>> Name | Version | Schema | Description
>
>> -+-++
x
> List of installed extensions
> Name | Version | Schema | Description
> -+-++--
> plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural
>
EXISTS citext WITH SCHEMA public;
CREATE EXTENSION
and as the superuser it shows up in the \dx display
BUT as a normal user:
stan=> \dx
List of installed extensions
Name | Version | Schema | Descript
On 7/11/19 6:54 AM, bhargav kamineni wrote:
Hi Team,
I have a doubt regarding the extensions.My db has these many extensions >
Name
---
adminpack
btree_gist
dblink
file_fdw
fuzzystrmatch
hstore
insert_username
intarray
pageinspect
pg_bufferca
Hi Team,
I have a doubt regarding the extensions.My db has these many extensions
Name
---
adminpack
btree_gist
dblink
file_fdw
fuzzystrmatch
hstore
insert_username
intarray
pageinspect
pg_buffercache
pg_freespacemap
pg_repack
pg_stat_statements
pg_trgm
On 11/15/18 3:23 PM, Lukáš Sobotka wrote:
Hi guys,
I would be grateful for some help. I am writing you because I am
confused about using data foreign wrappers and dblink. I attached
simplified script describing the problem.
What I am trying to do?
I have two databases and I need to copy tabl
=?UTF-8?B?THVrw6HFoSBTb2JvdGth?= writes:
> I would be grateful for some help. I am writing you because I am confused
> about using data foreign wrappers and dblink. I attached simplified script
> describing the problem.
I think what is happening is that postgres_fdw starts a transaction on
its co
Hi guys,
I would be grateful for some help. I am writing you because I am confused
about using data foreign wrappers and dblink. I attached simplified script
describing the problem.
What I am trying to do?
I have two databases and I need to copy table from local database to the
remote one. For co
> "GPT" == GPT writes:
GPT> Unfortunately, I had not installed the following package:
GPT> "postgresql-server-dev-11"
GPT> By the way, shouldn't a warning message appear while trying to run:
GPT> `PATH=/usr/lib/postgresql/11/bin:$PATH make USE_PGXS=1`
GPT> warning the user that some
GPT writes:
> Both PG versions 10.5 and 11 are installed.
> I have been trying to compile extensions for PG11 by using:
> PATH=/.../11/bin:PATH make USE_...
> but unfortunately PG10 is always being used (the `make` output always
> shows PG10 and refers to `pg_config`).
> 1)
les are missing.
Except there weren't. In $PATH there where the PG 10 files that could be
used. Now they where not the ones you wanted, but make did not 'know' that.
Tia
On 10/22/18, GPT wrote:
Hi,
Both PG versions 10.5 and 11 are installed.
I have been trying to compile exten
PT wrote:
> Hi,
>
> Both PG versions 10.5 and 11 are installed.
>
> I have been trying to compile extensions for PG11 by using:
>
> PATH=/.../11/bin:PATH make USE_...
>
> but unfortunately PG10 is always being used (the `make` output always
> shows PG10 and refers to
Hi,
Both PG versions 10.5 and 11 are installed.
I have been trying to compile extensions for PG11 by using:
PATH=/.../11/bin:PATH make USE_...
but unfortunately PG10 is always being used (the `make` output always
shows PG10 and refers to `pg_config`).
1) Does it have to do with pg_config?
2
and won't be dropped
> when it is. This is mainly because roles are cluster-wide but extensions
> are only local to one database. Consider for example what will happen
> when somebody tries to load your extension into more than one database in
> the same cluster.
Yes, that’s one
Alvar Freude writes:
> I have a question about best practices writing PostgreSQL extensions. Is it
> OK to write extensions which create users and grant/revoke rights on the
> created functions to this users?
I'd say that's generally deprecated. Per the documentation, y
Hi all,
I have a question about best practices writing PostgreSQL extensions. Is it OK
to write extensions which create users and grant/revoke rights on the created
functions to this users? Is it possible to add options to CREATE EXTENSION by
the extension itself e.g. to make user names
76 matches
Mail list logo
