On Mon, 2025-11-03 at 21:05 -0500, Bruce Momjian wrote:
> On Mon, Nov 3, 2025 at 07:42:06PM +0100, Laurenz Albe wrote:
>
> > Since you say that encrypting the temp files is the biggest hurdle for
> > community acceptance, what about a first version that does not encrypt
> > temp files? For one,
On 11/3/25 18:05, Bruce Momjian wrote:
On Mon, Nov 3, 2025 at 07:42:06PM +0100, Laurenz Albe wrote:
On Mon, 2025-11-03 at 11:56 -0500, Bruce Momjian wrote:
The problem with the Percona extension is it seems like it was developed
mostly/all by Percona employees, meaning development was driven/s
On Fri, Oct 10, 2025 at 8:58 PM sud wrote:>
> Thank you so much. That helps.
>
> I am planning to use pg_stat_get_backend_memory_contexts function
something as below by joining this to the pg_stat_activity. Hope this is
the right usage. Somehow i am getting an error stating the function doesn't
ex
On Mon, Nov 3, 2025 at 07:42:06PM +0100, Laurenz Albe wrote:
> On Mon, 2025-11-03 at 11:56 -0500, Bruce Momjian wrote:
> > The problem with the Percona extension is it seems like it was developed
> > mostly/all by Percona employees, meaning development was driven/steered
> > by Percona, and there
On 11/3/25 10:14, Bruce Momjian wrote:
On Mon, Nov 3, 2025 at 10:07:50AM -0800, Adrian Klaver wrote:
To be specific it is a customer service issue.
So why is this page:
https://www.postgresql.org/support/professional_support/
"Commercial support is available from many different companies
On Mon, 2025-11-03 at 11:56 -0500, Bruce Momjian wrote:
> The problem with the Percona extension is it seems like it was developed
> mostly/all by Percona employees, meaning development was driven/steered
> by Percona, and there was insufficient feedback from the community for
> it to be polished e
On Mon, 2025-11-03 at 16:39 +0100, [email protected] wrote:
> The HSM should be backed up, too. Which is only possible by connecting
> physically to it with a notebook and inserting an USB stick.
>
> Which begs the question: where do you source an USB stick with the same
> trust-level as th
On Mon, Nov 3, 2025 at 10:07:50AM -0800, Adrian Klaver wrote:
> On 11/3/25 8:59 AM, Bruce Momjian wrote:
> > On Mon, Nov 3, 2025 at 08:20:21AM -0800, Adrian Klaver wrote:
> > > On 11/3/25 08:01, Bruce Momjian wrote:
> > > > On Mon, Nov 3, 2025 at 04:39:45PM +0100, [email protected] wrote:
>
On 11/3/25 8:59 AM, Bruce Momjian wrote:
On Mon, Nov 3, 2025 at 08:20:21AM -0800, Adrian Klaver wrote:
On 11/3/25 08:01, Bruce Momjian wrote:
On Mon, Nov 3, 2025 at 04:39:45PM +0100, [email protected] wrote:
Am 2025-11-03 16:08, schrieb Bruce Momjian:
Again a distinction without
dfgpostgres writes:
> I want 9 records returned, each row with 3 cols, 1st col is the ctid,
> second is the column name, third is the val.
Perhaps psql's "expanded" mode is close enough?
regression=# \x
Expanded display is on.
regression=# select * from unpivot;
-[ RECORD 1 ]---
intcol | 1
flo
Wow !
That did it, even with the predicate I stuck on the end when I tried it.
Thanks Depesz !
On Mon, Nov 3, 2025 at 12:22 PM hubert depesz lubaczewski
wrote:
> On Mon, Nov 03, 2025 at 12:18:55PM -0500, dfgpostgres wrote:
> > psql (13.2, server 15.3) on linux
> >
> > I think they call this "un
On Mon, Nov 03, 2025 at 12:18:55PM -0500, dfgpostgres wrote:
> psql (13.2, server 15.3) on linux
>
> I think they call this "unpivot" in MSSQL ?
>
> How can I get an sql query to return one line per column with... an ID,
> column name and value. the ctid for the id field is fine.
>
> Example:
psql (13.2, server 15.3) on linux
I think they call this "unpivot" in MSSQL ?
How can I get an sql query to return one line per column with... an ID,
column name and value. the ctid for the id field is fine.
Example:
dvdb=# create table unpivot (intcol integer, floatcol float, strcol
varchar);
On Mon, Nov 3, 2025 at 08:20:21AM -0800, Adrian Klaver wrote:
> On 11/3/25 08:01, Bruce Momjian wrote:
> > On Mon, Nov 3, 2025 at 04:39:45PM +0100, [email protected] wrote:
> > > Am 2025-11-03 16:08, schrieb Bruce Momjian:
>
> > I will admit that companies are better at integrating with ext
On Sun, Nov 2, 2025 at 11:14:58AM +0100, Kai Wagner wrote:
> I fully agree here, and as I stated above, I don't question this at all, as
> this is the strength of the diverse and spread community. Looking at this
> thread alone, and the multiple different "users" popping up, that see the need
> an
Marcelo Fernandes writes:
> After doing some playing around with different operations against a numeric
> column, namely: increasing/decreasing the precision or increasing/decreasing
> the scale, I noticed that the table is rewritten in all cases except when
> increasing the precision number.
Yup
On 11/3/25 08:01, Bruce Momjian wrote:
On Mon, Nov 3, 2025 at 04:39:45PM +0100, [email protected] wrote:
Am 2025-11-03 16:08, schrieb Bruce Momjian:
I will admit that companies are better at integrating with external
vendors, particulary hardware vendors. There is an organization
misma
On Mon, Nov 3, 2025 at 04:39:45PM +0100, [email protected] wrote:
> Am 2025-11-03 16:08, schrieb Bruce Momjian:
>
> > Is it the Oracle API they don't like, that Postgres can improve upon, or
> > something fundamental they don't like, or don't see the value in?
>
>
> I am not sure.
>
> It
On 11/3/25 00:24, Marcelo Fernandes wrote:
Hi everyone,
A numeric field is defined as: NUMERIC(precision, scale) [0].
After doing some playing around with different operations against a numeric
column, namely: increasing/decreasing the precision or increasing/decreasing
the scale, I noticed tha
Am 2025-11-03 16:08, schrieb Bruce Momjian:
Is it the Oracle API they don't like, that Postgres can improve upon,
or
something fundamental they don't like, or don't see the value in?
I am not sure.
It just complicates everything.
Documentation isn't thin, it's skeletal.
And of course, actu
On Sat, Nov 1, 2025 at 09:07:01PM +0100, Rainer Duffner wrote:
> Do you actually have HSMs with your TDE (assuming you use it
> elsewhere? We run, for a customer, an Oracle DataGuard configuration
> with TDE with a HSM.
There were some interesting ideas in this email I want to reply to.
> We hav
My understanding is that Postgres can guarantee that all the values in the
table will fit the new precision without having to check. If you change the
scale, it might be the case that some values won’t fit anymore, and Postgres
must return an error. Numeric by itself is a variable length type, l
From: Marcelo Fernandes
Date: Monday, November 3, 2025 at 5:24 AM
To: [email protected]
Subject: Increasing a NUMERIC column precision doesn't cause a table rewrite.
Why?
Hi everyone,
A numeric field is defined as: NUMERIC(precision, scale) [0].
After doing some playing around
Hi everyone,
A numeric field is defined as: NUMERIC(precision, scale) [0].
After doing some playing around with different operations against a numeric
column, namely: increasing/decreasing the precision or increasing/decreasing
the scale, I noticed that the table is rewritten in all cases except
24 matches
Mail list logo
