Ok, thanks for the clarification. Any particular reason for the change of
plans? Would it come in 17?
Thanks
Tony
On Wed, May 17, 2023, 5:49 PM Bruce Momjian wrote:
> On Wed, May 17, 2023 at 03:35:39PM -0700, Tony Xu wrote:
> > Hi There,
> >
> > The FAQ (copied below) mentioned that native tran
Maciek Sakrejda writes:
> The pg_stats.avg_width field is documented [1] as "Average width in
> bytes of column's entries" but it's not defined exactly what "entries"
> means here with respect to STORAGE (the underlying pg_statistic
> documentation doesn't clarify this either). I thought initially
Hello,
The pg_stats.avg_width field is documented [1] as "Average width in
bytes of column's entries" but it's not defined exactly what "entries"
means here with respect to STORAGE (the underlying pg_statistic
documentation doesn't clarify this either). I thought initially this
was the "logical" s
On Wed, May 17, 2023 at 03:35:39PM -0700, Tony Xu wrote:
> Hi There,
>
> The FAQ (copied below) mentioned that native transparent data encryption might
> be included in 16. Is it fair to assume that it will support database level
> encryption, that is, we can use two encryption keys for two databa
Hi There,
The FAQ (copied below) mentioned that native transparent data encryption
might be included in 16. Is it fair to assume that it will support database
level encryption, that is, we can use two encryption keys for two databases
in the same server, respectively? How can one verify that?
Tha
Hi,
On 2023-05-17 11:36:37 +0530, Shubham Dhama wrote:
> > consistent_point (text)
> > The WAL location at which the slot became consistent. This is the earliest
> > location from which streaming can start on this replication slot.
>
> But it doesn't seem true in my scenario. Here is how to repr
On Wed, 2023-05-17 at 08:21 +0200, hubert depesz lubaczewski wrote:
> On Wed, May 17, 2023 at 08:16:41AM +0200, Laurenz Albe wrote:
> > On Tue, 2023-05-16 at 19:35 +0200, hubert depesz lubaczewski wrote:
> > > > I'm working on a workaround for a bug in Pg
> > > > (https://www.postgresql.org/message
Avi Weinberg writes:
> I noticed this problem when creating a backup on Postgres 13 and restoring it
> on Postgres 15.
> CREATE FUNCTION sync.show_pg_subscription1() RETURNS SETOF
> pg_subscription
> LANGUAGE sql
> AS $$
> SELECT * from pg_subscri
On Tue, 16 May 2023 23:30:42 +0200
Marcello Lorenzi wrote:
> Hi everyone,
> we're looking for the best solution for a 2-nodes cluster in HA with
> Postegresql 15. after some checks we are noticed about pgpool for the
> management of balancing and automatic failover. Can it be considered a
> viabl
On Sun, May 14, 2023 at 2:20 AM Kirk Wolak wrote:
> On Sat, May 13, 2023 at 3:34 PM Jeremy Smith
> wrote:
>
>>
>>
>> On Sat, May 13, 2023, 3:25 AM Kirk Wolak wrote:
>>
>>> Does this imply SQL SYNTAX like:
>>>
>>> SHOW CREATE TABLE
>>> [ INCLUDING { ALL | INDEXES | SEQUENCES | ??? }]
>>> [
On 17/05/2023 1:39 am, Andres Freund wrote:
> Try to prevent the DROP DATABASE from getting cancelled :/.
I still don't know why that's happening. I mean, I know why it gets
cancelled (the client timeout we set in Npgsql), but I don't know why
the drop does not succeed within 30 seconds. We could,
11 matches
Mail list logo
