On Tue, Sep 26, 2023 at 1:15 PM Tom Lane wrote
> it clear that the type exists independently of the function. (Our
> behavior of automatically making composite types for tables seems to
> me to have been a rather unfortunate choice.)
>
I really like this behavior and exploit it heavily, in
Philip Carlsen writes:
> I've been down a rabbit hole today trying to understand what exactly makes
> a type a valid candidate for an ANYARRAY function argument (e.g., something
> you can 'unnest()').
Per the comments for check_generic_type_consistency:
* 2) All arguments declared ANYARRAY
We download the ODBC source from http://ftp.postgresql.org and build it
on-site, 13.02. in this case.
A colleague noticed that the following files in the psqlODBC MSI for Windows
have no version numbers:
pgenlist.dll
pgenlista.dll
pgxalib.dll
Does anyone know if that is be design or just
On 27-09-2023 04:03, Erik Wienhold wrote:
ccing list
On 2023-09-27 00:12 +0200, dld write:
On 26-09-2023 23:47, Erik Wienhold wrote:
On 2023-09-26 14:44 +0200, dld wrote:
I followed the discussion about the schema resolution, and I really think
there is need for an early bound (at function
On Tue, 2023-09-26 at 21:39 +0200, Philip Carlsen wrote:
> I've been down a rabbit hole today trying to understand what exactly makes a
> type
> a valid candidate for an ANYARRAY function argument (e.g., something you can
> 'unnest()').
>
> My reading has led me across such functions as
Hi list
I've been down a rabbit hole today trying to understand what exactly makes
a type a valid candidate for an ANYARRAY function argument (e.g., something
you can 'unnest()').
My reading has led me across such functions as 'get_promoted_array_type',
'IsTrueArrayType', 'can_coerce_type', and
Alexander Petrossian writes:
> 25 сент. 2023 г., в 17:28, Tom Lane написал(а):
>> you’d have a big problem with being able to change the behavior of
>> security-definer functions.
> Could you please elaborate on this, Tom?
pldebugger allows you to change the contents of a function's
local
> 25 сент. 2023 г., в 17:28, Tom Lane написал(а):
> Alexander Petrossian writes:
I am wondering why is this, why not allow debugging for non-privileged
users?
> Even if there's a way to restrict
> debugging connections to sessions owned by the same user,
I guess, there is such a way.
On 2023-09-27 11:53 +0200, Somnath Som write:
> "analyze_new_cluster.sh" this features is available for PostgreSQL version
> 15.4 ?
No. That was already removed in 14.0. pg_upgrade now just instructs
you to run vacuumdb directly.
--
Erik
Hi Team,
"analyze_new_cluster.sh" this features is available for PostgreSQL version 15.4
?
First of all please use reply all so that everyone sees the answers.
Not sure since PgObject is certainly in the jdbc jar.
pgjdbc/pgjdbc/src/main/java/org/postgresql/util/PGobject.java
at 5709a20fbef453749d2394e11502527e4a3ab5bb · pgjdbc/pgjdbc (github.com)
On Wed, 2023-09-27 at 00:01 +0530, Atul Kumar wrote:
> my postgres version is 12 and running on centos 7
>
> my log_statement is set to "DDL".
>
> and log_min_duration_statement is set to "1ms"
>
> so technically it should log "ONLY DDLs" that take more than 1ms.
>
> but to my surprise,
12 matches
Mail list logo
