Re: Content for talk on Postgres Type System at PostgresConf

[Laurenz Albe]

On Thu, 2024-02-29 at 13:38 -0800, Guyren Howe wrote:
> what are the misconceptions, or where might I find them for  myself?

In addition to what was already said:

> My current understanding:
>  * character is fixed-length, blank-padded. Not sure when you’d
>want that, but it seems clear. Is the name just confusing?

I find the semantics confusing:

  test=> SELECT 'a'::character(10);
 bpchar   
  
   a 
  (1 row)

Ok, it is 10 characters long.

  test=> SELECT length('a'::character(10));
   length 
  
1
  (1 row)

Or is it?

  test=> SELECT 'a'::character(10) || 'b'::character(10);
   ?column? 
  ══
   ab
  (1 row)

And why is the result not 20 characters long, with spaces between "a" and "b"?

Best avoid "character".

>  * timestamptz is just converted to a timestamp in UTC. Folks might
>imagine that it stores the time zone but it doesn’t.

Yes, and I find that lots of people are confused by that.

You could talk about the interaction with the "timezone" parameter, and
that it is not so much a timestamp with time zone, but an "absolute timestamp",
and in combination with "timestamp" a great way to let the database handle
the difficult task of time zone conversion for you.

Yours,
Laurenz Albe

RE: Unable to get PostgreSQL 15 with Kerberos (GSS) working

[Matthew Dennison]

Host file looks like:

127.0.0.1   localhost hostname hostname.mydomain.net
::1 localhost hostname hostname.mydomain.net
10.204.50.65 hostname hostname.mydomain.net

I also tried commenting out the ::1 line, but the issue moved to 127.0.0.1, 
commented that out and the issue moved to the IP.  I really don’t get it.  
However, when I finally realised it was a localised issue (after days) I was 
able to move forward.  No idea why it will not work on the server itself, but 
it is something I can live with.

Regards

Matt Dennison
From: Rob Sargent 
Sent: Thursday, February 29, 2024 2:56 PM
To: pgsql-general@lists.postgresql.org
Subject: Re: Unable to get PostgreSQL 15 with Kerberos (GSS) working


On 2/29/24 01:18, Matthew Dennison wrote:

Here's the results:



psql: error: connection to server at "hostname.mydomain.net" (::1), port 5432 
failed: GSSAPI continuation error: Unspecified GSS failure.  Minor code may 
provide more information: No Kerberos credentials available (default cache: 
KCM:)



If I run kinit and get Kerberos ticket ahead of running the command I then 
receive:



psql: error: connection to server at " hostname.mydomain.net " (::1), port 5432 
failed: could not initiate GSSAPI security context: Unspecified GSS failure.  
Minor code may provide more information: Server not found in Kerberos database

connection to server at " hostname.mydomain.net " (::1), port 5432 failed: 
GSSAPI continuation error: Unspecified GSS failure.  Minor code may provide 
more information: Server not found in Kerberos database




Should a FQDN resolve to ::1?

Re: Excel Source [24]] Error: System.Exception: SqlTruncateException: Numeric arithmetic causes

[felix . quintgz]

The numeric(19, 18) field type can only store numbers less than 10 with 18 
decimal places.
To save the number 36655.63 you need a numeric(12, 2) field type.


 On Thursday, February 29, 2024 at 10:00:10 AM GMT-5, Erik Wienhold 
 wrote:

 cc'ing list.

On 2024-02-29 07:16 +0100, Anthony Apollis wrote:
> I cant change data type using the advance editor in destination:
> [image: image.png]
> [image: image.png]

The column type must be changed in the database itself.

On second thought, are you sure "Metric Value" is the right destination
column for your import?  Maybe type numeric(19,18) is intentional.

> On Thu, 29 Feb 2024 at 08:11, Anthony Apollis 
> wrote:
>
> > I tried multiple data types, including: "Metric Value" text COLLATE
> > pg_catalog."default", "Metric Value" character varying(510) COLLATE
> > pg_catalog."default", and Decimal/Numeric.

Did you get the same error with the text columns?  In plain SQL you can
certainly insert numeric into text columns.  Postgres does an implicit
cast in that case.  Not sure what your middleware does in that case
though.

> > On Thu, 29 Feb 2024 at 02:12, Erik Wienhold  wrote:
> >
> >> On 2024-02-28 21:22 +0100, Anthony Apollis wrote:
> >> > Please assist. I am using SSIS to read data from an Excel sheet into
> >> > Postgres. I have increased the column size a few times, just cant seem
> >> to
> >> > get the data in. Getting errors relating to destination column size.
> >>
> >> What is the data type of that column?
> >>
> >> > [Excel Source [24]] Error: System.Exception: SqlTruncateException:
> >> > Numeric arithmetic causes truncation.. RowNumber=1, ColumnName=Metric
> >> > Value [DataType=DT_NUMERIC,Length=0], Data=[Length=12,
> >> > Value=36655.63]
> >> >    at
> >> ZappySys.PowerPack.Adapter.SqlDataComponentBase.HandleException(Exception
> >> > ex)
> >> >    at ZappySys.PowerPack.Adapter.SqlDataComponentBase.PrimeOutput(Int32
> >> > outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
> >> >    at
> >> Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100
> >> > wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers,
> >> > IntPtr ppBufferWirePacket)
> >>
> >> Not sure what I'm looking at, but screenshots 1 and 2 say precision=19
> >> and scale=18 which would be numeric(19,18).  But value 36655.63
> >> shown in the error message requires a precision that is at least 9
> >> digits larger than the scale:
> >>
> >>        regress=# select '36655.63'::numeric(19,18);
> >>        ERROR:  numeric field overflow
> >>        DETAIL:  A field with precision 19, scale 18 must round to an
> >> absolute value less than 10^1.
> >>        regress=# select '36655.63'::numeric(27,18);
> >>                    numeric
> >>        --
> >>          36655.63
> >>        (1 row)

--
Erik

Re: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL]

[Miguel Manzano]

  Ccc.  blowjobsblowjobsblowjobsblowjobsblowjobsblowjobsBuenos días . Por
favor queria hacer un pedido de 2 salteñas de carne picante y 2 de pollo
picante para ir a recoger a la 1 de la tarde por favor.
Graciasblowjobhttps://whatsapp.com/channel/0029Va94dZyIXnlxXagThf0G

Lea también
sBuenos días . Por favor queria hacer un pedido de 2 salteñas de carne
picante y 2 de pollo picante para ir a recoger a la 1 de la tarde por
favor. GraciasBuenos días . Por favor queria hacer un pedido de 2 salteñas
de carne picante y 2 de pollo picante para ir a recoger a la 1 de la tarde
por favor. GraciasblowjobsBuenos días . Pblowjobsor Buenos días . Por favor
queria hacer un pedido de 2 salteñas de carne picante y 2 de pollo picante
para ir a recoger a la 1 de la tarde por favor. Graciasfavor queria hacer
un pedido de 2 salteñas de carne picante y 2 de pollo picante para ir a
recoger a la 1 de la tarde por favor. GraciasBuenos días . Por favor queria
hacer un pedido de 2 salteñas de carne picante y 2 de pollo picante para ir
a recoger a la 1 de la tarde por favor. GraciasBuenos días . Por favor
queria hacer un pedido de 2 salteñas de carne picante y 2 de pollo picante
para ir a recoger a la 1 de la tarde por favor. Gracias

El jue, 29 de feb de 2024, 21:37, Kyotaro Horiguchi 
escribió:

> Hi, Mark.
>
> At Thu, 29 Feb 2024 04:39:49 +, Mark Schloss <
> mark.schl...@austrac.gov.au> wrote in
> > Thanks for looking at this. I think I complicated things by
> > including barman. I was just wanting to point out each primary
> > streams to two locations - the walreceiver on the replica and the
> > walreciver used by barman. We think the reason the barman
> > WAL-receiver didn't fail is because there is no apply of the WAL in
> > Barman but the Standby is applying and it's WAL-receiver got
> > terminated, so the barman server can be taken out of this picture
> > completely, they were just there as a by-product in trying to
> > determine the effect.  We are only interested in the killing of the
> > standby wal-receiver and that the pg_waldump showed the failing lsn
> > was a commit.
>
> It seems that an issue raised in the -hackers thread [1] might be the
> same issue as yours. The discussion might be a help for you, although
> it's not clear what is happening yet.
>
> [1]
> https://www.postgresql.org/message-id/CAFh8B%3DmozC%2Be1wGJq0H%3D0O65goZju%2B6ab5AU7DEWCSUA2OtwDg%40mail.gmail.com
>
> regards.
>
> --
> Kyotaro Horiguchi
> NTT Open Source Software Center
>
>
>

Re: Content for talk on Postgres Type System at PostgresConf

[Adrian Klaver]

On 3/1/24 01:18, Laurenz Albe wrote:

On Thu, 2024-02-29 at 13:38 -0800, Guyren Howe wrote:

what are the misconceptions, or where might I find them for  myself?


In addition to what was already said:


My current understanding:
  * character is fixed-length, blank-padded. Not sure when you’d
want that, but it seems clear. Is the name just confusing?


I find the semantics confusing:

   test=> SELECT 'a'::character(10);
  bpchar
   
a
   (1 row)

Ok, it is 10 characters long.

   test=> SELECT length('a'::character(10));
length
   
 1
   (1 row)

Or is it?


https://www.postgresql.org/docs/current/datatype-character.html

"Values of type character are physically padded with spaces to the 
specified width n, and are stored and displayed that way. However, 
trailing spaces are treated as semantically insignificant and 
disregarded when comparing two values of type character. In collations 
where whitespace is significant, this behavior can produce unexpected 
results; for example SELECT 'a '::CHAR(2) collate "C" < E'a\n'::CHAR(2) 
returns true, even though C locale would consider a space to be greater 
than a newline. Trailing spaces are removed when converting a character 
value to one of the other string types. Note that trailing spaces are 
semantically significant in character varying and text values, and when 
using pattern matching, that is LIKE and regular expressions."




   test=> SELECT 'a'::character(10) || 'b'::character(10);
?column?
   ══
ab
   (1 row)

And why is the result not 20 characters long, with spaces between "a" and "b"?


SELECT pg_typeof('a'::character(10) || 'b'::character(10));
 pg_typeof
---
 text

This is covered by  "Trailing spaces are removed when converting a 
character value to one of the other string types.".


Though that still leaves you with:

SELECT pg_typeof(('a'::character(10) || 'b'::character(10))::char(20));
 pg_typeof
---
 character

SELECT ('a'::character(10) || 'b'::character(10))::char(20);
bpchar
--
 ab





Best avoid "character".


  * timestamptz is just converted to a timestamp in UTC. Folks might
imagine that it stores the time zone but it doesn’t.


Yes, and I find that lots of people are confused by that.

You could talk about the interaction with the "timezone" parameter, and
that it is not so much a timestamp with time zone, but an "absolute timestamp",
and in combination with "timestamp" a great way to let the database handle
the difficult task of time zone conversion for you.

Yours,
Laurenz Albe





--
Adrian Klaver
adrian.kla...@aklaver.com

Re: Content for talk on Postgres Type System at PostgresConf

[grimy . outshine830]

On Thu, Feb 29, 2024 at 05:51:11PM -0500, Tom Lane wrote:

> >> money is a fixed-point decimal value, the number of decimal
> >> places is locale determined. I’m not aware of any particular
> >> problems with that

> > You forget about the currency symbol dynamic. Like with time zones
> > the local session provides the context, not the stored data.

> Yeah.  The fact that the same stored value might look like 10.00
> euros to one session and 1000 yen to another one is pretty
> catastrophic.  The other nasty thing about money is that it's an
> int64 so it can't represent more than 2^63 pennies (for whatever a
> "penny" is).  Now, that's still a Frickin Lot Of Money in any
> non-hyperinflated currency, but it's the sort of restriction that
> banks don't like to hear of.

Lame excuse first: I have never used the money type, probably because
I overheard a word like "catastrophic" in my early development :-)

But, doesn't what Tom says above contradict Adrian's example session?
Either the stored value is re-interpreted according to the locale
context, or it isn't. IMO it would be *more* catastrophic if it wasn't,
as it looks from Adrian's example.

-- 
Ian

How to clone a database?

[normandavis1990]

Hello,
I have a primary server with two replication servers. I want to HA this primary 
server because I need to shut it down. Please introduce me to a tutorial that 
explains this step by step.
Could setting up HA cause the primary server to go down?

Cheers.

Re: High Availability and Replication

[normandavis1990]

> On Thursday, February 29th, 2024 at 11:38 PM, Israel Brewster 
>  wrote:

>> On Feb 29, 2024, at 10:15 AM, David G. Johnston  
>> wrote:
>>
>> On Thursday, February 29, 2024, normandavis1990  
>> wrote:
>>
>>> What is the difference between High Availability and Replication?
>>
>> The former is a goal, the later is a technique.
>
> Perhaps more specifically: Replication is simply Replicating - or copying - 
> the “master” database to one or more “slave” databases, generally in 
> real-time such that the slave database clusters are replicas of the master. 
> This is good when the master goes down, because you’ll still have one or more 
> copies of it available, but by itself it doesn’t keep there from being an 
> outage if/when the master goes down.
>
> High Availability layers on top of replication to provide some means of 
> ensuring that the database is HIGHLY available, such as an automatic failover 
> system or load balancer. Many different options that work in many different 
> ways are available to help meet this goal.
> ---
> Israel Brewster
> Software Engineer
> Alaska Volcano Observatory
> Geophysical Institute - UAF
> 2156 Koyukuk Drive
> Fairbanks AK 99775-7320
> Work: 907-474-5172
> cell: 907-328-9145
>
>> David J.

Hi,
You said "This is good when the master goes down, because you’ll still have one 
or more copies of it available, but by itself it doesn’t keep there from being 
an outage if/when the master goes down.". What does "goes down" mean?
In Replication mode, if the primary server is shut down, then the data will 
also be lost?

Re: High Availability and Replication

[Israel Brewster]

> On Mar 1, 2024, at 11:36 AM, normandavis1990  
> wrote:
> 
> > On Thursday, February 29th, 2024 at 11:38 PM, Israel Brewster 
> >  wrote:
>>> On Feb 29, 2024, at 10:15 AM, David G. Johnston 
>>>  wrote:
>>> 
>>> 
>>> 
>>> On Thursday, February 29, 2024, normandavis1990 >> > wrote:
 
 What is the difference between High Availability and Replication?
>>> 
>>> The former is a goal, the later is a technique.
>> 
>> Perhaps more specifically: Replication is simply Replicating - or copying - 
>> the “master” database to one or more “slave” databases, generally in 
>> real-time such that the slave database clusters are replicas of the master. 
>> This is good when the master goes down, because you’ll still have one or 
>> more copies of it available, but by itself it doesn’t keep there from being 
>> an outage if/when the master goes down.
>> 
>> High Availability layers on top of replication to provide some means of 
>> ensuring that the database is HIGHLY available, such as an automatic 
>> failover system or load balancer. Many different options that work in many 
>> different ways are available to help meet this goal.
>> ---
>> Israel Brewster
>> Software Engineer
>> Alaska Volcano Observatory 
>> Geophysical Institute - UAF 
>> 2156 Koyukuk Drive 
>> Fairbanks AK 99775-7320
>> Work: 907-474-5172
>> cell:  907-328-9145
>> 
>>> 
>>> David J.
>>>  
>> 
> 
> 
> Hi,
> You said "This is good when the master goes down, because you’ll still have 
> one or more copies of it available, but by itself it doesn’t keep there from 
> being an outage if/when the master goes down.". What does "goes down" mean?

Exactly what I said - it goes down. Not functioning. Offline. Inaccessible. It 
is not up and running, therefore, it is down.

> In Replication mode, if the primary server is shut down, then the data will 
> also be lost?

No. As I said - and you quoted - “When the master goes down…you’ll still have 
one or more copies of it available”. So no, the data will NOT be lost.

---
Israel Brewster
Software Engineer
Alaska Volcano Observatory 
Geophysical Institute - UAF 
2156 Koyukuk Drive 
Fairbanks AK 99775-7320
Work: 907-474-5172
cell:  907-328-9145

Re: High Availability and Replication

[Abdul Sayeed]

Hi,

When Master server goes down, either you need to promote one of slave node
or configure HA mechanism so that in case of master server goes down it
will automatically promote the slave server as new master.

Patroni HA tool would be good option for your requirement.

https://patroni.readthedocs.io/en/latest/README.html

Hope this helps.



Thanks & Regards,
Abdul Sayeed
PostgreSQL DBA



On Sat, 2 Mar 2024 at 2:15 AM, Israel Brewster 
wrote:

> On Mar 1, 2024, at 11:36 AM, normandavis1990 
> wrote:
>
> > On Thursday, February 29th, 2024 at 11:38 PM, Israel Brewster <
> ijbrews...@alaska.edu> wrote:
>
> On Feb 29, 2024, at 10:15 AM, David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>
>
> On Thursday, February 29, 2024, normandavis1990 
> wrote:
>
>>
>> What is the difference between High Availability and Replication?
>>
>
> The former is a goal, the later is a technique.
>
>
> Perhaps more specifically: Replication is simply Replicating - or copying
> - the “master” database to one or more “slave” databases, generally in
> real-time such that the slave database clusters are replicas of the master.
> This is good when the master goes down, because you’ll still have one or
> more copies of it available, but by itself it doesn’t keep there from being
> an outage if/when the master goes down.
>
> High Availability layers on top of replication to provide some means of
> ensuring that the database is HIGHLY available, such as an automatic
> failover system or load balancer. Many different options that work in many
> different ways are available to help meet this goal.
> ---
> Israel Brewster
> Software Engineer
> Alaska Volcano Observatory
> Geophysical Institute - UAF
> 2156 Koyukuk Drive
> 
>
> Fairbanks AK 99775-7320
> 
> Work: 907-474-5172
> cell:  907-328-9145
>
>
> David J.
>
>
>
>
> Hi,
> You said "This is good when the master goes down, because you’ll still
> have one or more copies of it available, but by itself it doesn’t keep
> there from being an outage if/when the master goes down.". What does "goes
> down" mean?
>
>
> Exactly what I said - it goes down. Not functioning. Offline.
> Inaccessible. It is not up and running, therefore, it is down.
>
> In Replication mode, if the primary server is shut down, then the data
> will also be lost?
>
>
> No. As I said - and you quoted - “When the master goes down…you’ll still
> have one or more copies of it available”. So no, the data will NOT be lost.
>
> ---
> Israel Brewster
> Software Engineer
> Alaska Volcano Observatory
> Geophysical Institute - UAF
> 2156 Koyukuk Drive
> 
>
> Fairbanks AK 99775-7320
> 
> Work: 907-474-5172
> cell:  907-328-9145
>
>

Re: High Availability and Replication

[normandavis1990]

> On Saturday, March 2nd, 2024 at 12:14 AM, Israel Brewster 
>  wrote:

>> On Mar 1, 2024, at 11:36 AM, normandavis1990  
>> wrote:
>>
>>> On Thursday, February 29th, 2024 at 11:38 PM, Israel Brewster 
>>>  wrote:
>>
 On Feb 29, 2024, at 10:15 AM, David G. Johnston 
  wrote:

 On Thursday, February 29, 2024, normandavis1990 
  wrote:

> What is the difference between High Availability and Replication?

 The former is a goal, the later is a technique.
>>>
>>> Perhaps more specifically: Replication is simply Replicating - or copying - 
>>> the “master” database to one or more “slave” databases, generally in 
>>> real-time such that the slave database clusters are replicas of the master. 
>>> This is good when the master goes down, because you’ll still have one or 
>>> more copies of it available, but by itself it doesn’t keep there from being 
>>> an outage if/when the master goes down.
>>>
>>> High Availability layers on top of replication to provide some means of 
>>> ensuring that the database is HIGHLY available, such as an automatic 
>>> failover system or load balancer. Many different options that work in many 
>>> different ways are available to help meet this goal.
>>> ---
>>> Israel Brewster
>>> Software Engineer
>>> Alaska Volcano Observatory
>>> Geophysical Institute - UAF
>>> 2156 Koyukuk Drive
>>> Fairbanks AK 99775-7320
>>> Work: 907-474-5172
>>> cell: 907-328-9145
>>>
 David J.
>>
>> Hi,
>> You said "This is good when the master goes down, because you’ll still have 
>> one or more copies of it available, but by itself it doesn’t keep there from 
>> being an outage if/when the master goes down.". What does "goes down" mean?
>
> Exactly what I said - it goes down. Not functioning. Offline. Inaccessible. 
> It is not up and running, therefore, it is down.
>
>> In Replication mode, if the primary server is shut down, then the data will 
>> also be lost?
>
> No. As I said - and you quoted - “When the master goes down…you’ll still have 
> one or more copies of it available”. So no, the data will NOT be lost.
>
> ---
> Israel Brewster
> Software Engineer
> Alaska Volcano Observatory
> Geophysical Institute - UAF
> 2156 Koyukuk Drive
> Fairbanks AK 99775-7320
> Work: 907-474-5172
> cell: 907-328-9145

Hi,
Therefore, in both HA and Replication, when the primary server is shut down, 
the information is not lost, and the only difference is that in the HA 
mechanism, another server replaces the primary one, but this is not the case in 
Replication. Is it true?

Re: High Availability and Replication

[normandavis1990]

> On Saturday, March 2nd, 2024 at 1:24 AM, Abdul Sayeed 
>  wrote:

> Hi,
>
> When Master server goes down, either you need to promote one of slave node or 
> configure HA mechanism so that in case of master server goes down it will 
> automatically promote the slave server as new master.
>
> Patroni HA tool would be good option for your requirement.
>
> https://patroni.readthedocs.io/en/latest/README.html
>
> Hope this helps.
>
> Thanks & Regards,
> Abdul Sayeed
> PostgreSQL DBA
>
> On Sat, 2 Mar 2024 at 2:15 AM, Israel Brewster  wrote:
>
>>> On Mar 1, 2024, at 11:36 AM, normandavis1990  
>>> wrote:
>>>
 On Thursday, February 29th, 2024 at 11:38 PM, Israel Brewster 
  wrote:
>>>
> On Feb 29, 2024, at 10:15 AM, David G. Johnston 
>  wrote:
>
> On Thursday, February 29, 2024, normandavis1990 
>  wrote:
>
>> What is the difference between High Availability and Replication?
>
> The former is a goal, the later is a technique.

 Perhaps more specifically: Replication is simply Replicating - or copying 
 - the “master” database to one or more “slave” databases, generally in 
 real-time such that the slave database clusters are replicas of the 
 master. This is good when the master goes down, because you’ll still have 
 one or more copies of it available, but by itself it doesn’t keep there 
 from being an outage if/when the master goes down.

 High Availability layers on top of replication to provide some means of 
 ensuring that the database is HIGHLY available, such as an automatic 
 failover system or load balancer. Many different options that work in many 
 different ways are available to help meet this goal.
 ---
 Israel Brewster
 Software Engineer
 Alaska Volcano Observatory
 Geophysical Institute - UAF
 [2156 Koyukuk 
 Drive](https://www.google.com/maps/search/2156+Koyukuk+Drive+Fairbanks+AK+99775-7320?entry=gmail)
 [Fairbanks AK 
 99775-7320](https://www.google.com/maps/search/2156+Koyukuk+Drive+Fairbanks+AK+99775-7320?entry=gmail)
 Work: 907-474-5172
 cell: 907-328-9145

> David J.
>>>
>>> Hi,
>>> You said "This is good when the master goes down, because you’ll still have 
>>> one or more copies of it available, but by itself it doesn’t keep there 
>>> from being an outage if/when the master goes down.". What does "goes down" 
>>> mean?
>>
>> Exactly what I said - it goes down. Not functioning. Offline. Inaccessible. 
>> It is not up and running, therefore, it is down.
>>
>>> In Replication mode, if the primary server is shut down, then the data will 
>>> also be lost?
>>
>> No. As I said - and you quoted - “When the master goes down…you’ll still 
>> have one or more copies of it available”. So no, the data will NOT be lost.
>>
>> ---
>> Israel Brewster
>> Software Engineer
>> Alaska Volcano Observatory
>> Geophysical Institute - UAF
>> [2156 Koyukuk 
>> Drive](https://www.google.com/maps/search/2156+Koyukuk+Drive+Fairbanks+AK+99775-7320?entry=gmail)
>> [Fairbanks AK 
>> 99775-7320](https://www.google.com/maps/search/2156+Koyukuk+Drive+Fairbanks+AK+99775-7320?entry=gmail)
>> Work: 907-474-5172
>> cell: 907-328-9145

Hi,
Does installing Patroni cause the primary server to stop even for a short time?

Guarantees/Semantics of pg_stats

[Baziotis, Stefanos]

Hi,

I'm interested in learning more about the guarantees/semantics of pg_stats. For 
example, is there a guarantee that the n_distinct and most_common_vals fields 
will take into account any values appearing more than M times or maybe with 
frequence more than f? In what cases will n_distinct and most_common_vals will 
miss some values?

Any pointers to documentation or source code would be greatly appreciated.

Best,
Stefanos