Re: Should we really recommend "-A md5 or -A password"?

On Tue, May 31, 2022 at 3:57 PM Jonathan S. Katz wrote: > On 5/31/22 8:35 AM, Magnus Hagander wrote: > > > > > > On Tue, May 31, 2022 at 2:29 PM Daniel Westermann (DWE) > > > > wrote: > > > > Hi, > > > > I just came across this: > > "Also,

Re: Can we still dump version 7?

On 5/31/22 12:21 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On 5/31/22 10:55 AM, Tom Lane wrote: I wonder whether we should update this or just remove it --- it's clearly something that's likely to get missed again. While burdensome, +1 for updating. We don't want users to get caught

Re: CREATE EXTENSION not adding extension on second SCHEMA

Thank you so much guys, my mistake I didn't pay attention. I'm new to PostgreSQL and your help is much appreciated! Em ter., 31 de mai. de 2022 às 12:32, Tom Lane escreveu: > "David G. Johnston" writes: > > On Tuesday, May 31, 2022, PG Doc comments form > > wrote: > >> I'm trying to add an

Re: Can we still dump version 7?

"Jonathan S. Katz" writes: > On 5/31/22 10:55 AM, Tom Lane wrote: >> I wonder whether we should update this or just remove it --- it's >> clearly something that's likely to get missed again. > While burdensome, +1 for updating. We don't want users to get caught by > surprise if pg_dumpall does

Re: Can we still dump version 7?

>> >> Ugh, missed that, thanks for spotting it. >> I wonder whether we should update this or just remove it --- it's >> clearly something that's likely to get missed again. >While burdensome, +1 for updating. We don't want users to get caught by >surprise if pg_dumpall does not work on an old

Re: CREATE EXTENSION not adding extension on second SCHEMA

"David G. Johnston" writes: > On Tuesday, May 31, 2022, PG Doc comments form > wrote: >> I'm trying to add an extension to two schemas that I have in my DB. > It doesn’t work and isn’t documented as something that does work. I really > don’t see a need to say you cannot install the same

Fwd: Adding more detail to pg_upgrade documentation

Hi, We are upgrading from Postgres 11 to 13. During upgrade we found that the physical slots on the old cluster are not copied to the new cluster. This information is not mentioned in the documentation - https://www.postgresql.org/docs/13/pgupgrade.html Just thought it would be good to have

Re: CREATE EXTENSION not adding extension on second SCHEMA

On Tuesday, May 31, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-createextension.html > Description: > > I'm trying to add an extension to two schemas that I have in my DB. > > steps: > >

Re: CREATE EXTENSION not adding extension on second SCHEMA

quote from manual: > CREATE EXTENSION loads a new extension into the current database. There > must not be an extension of the same name already loaded. > You can try to alter[1] the extension to make it located to another schema. [1]: https://www.postgresql.org/docs/14/sql-alterextension.html

CREATE EXTENSION not adding extension on second SCHEMA

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/sql-createextension.html Description: I'm trying to add an extension to two schemas that I have in my DB. steps: 1) CREATE EXTENSION unaccent with SCHEMA public; response: OK. 2)

Re: Can we still dump version 7?

On 5/31/22 10:55 AM, Tom Lane wrote: "Daniel Westermann (DWE)" writes: I guess this statement is not true anymore? "Current releases of the dump programs can read data from any server version back to 7.0." https://www.postgresql.org/docs/current/upgrading.html Ugh, missed that, thanks for

Re: Can we still dump version 7?

"Daniel Westermann (DWE)" writes: > I guess this statement is not true anymore? > "Current releases of the dump programs can read data from any server version > back to 7.0." > https://www.postgresql.org/docs/current/upgrading.html Ugh, missed that, thanks for spotting it. I wonder whether we

Can we still dump version 7?

Hi, this commit (64f3524e2c8deebc02808aa5ebdfa17859473add) removed dump support for dumping from pre-8.0. I guess this statement is not true anymore? "Current releases of the dump programs can read data from any server version back to 7.0."

Re: Should we really recommend "-A md5 or -A password"?

>> Yes I think we absolutely should! >+1 >Proposed patch attached. This also removes "-A password" from that >sentence as well. You've been faster than me :) Looks good. Regards Daniel

Re: Should we really recommend "-A md5 or -A password"?

On 5/31/22 8:35 AM, Magnus Hagander wrote: On Tue, May 31, 2022 at 2:29 PM Daniel Westermann (DWE) > wrote: Hi, I just came across this: "Also, specify -A md5 or -A password so that the default trust authentication mode is not

Re: Should we really recommend "-A md5 or -A password"?

On Tue, May 31, 2022 at 2:29 PM Daniel Westermann (DWE) < daniel.westerm...@dbi-services.com> wrote: > Hi, > > I just came across this: > "Also, specify -A md5 or -A password so that the default trust > authentication mode is not used;" >

Should we really recommend "-A md5 or -A password"?

Hi, I just came across this: "Also, specify -A md5 or -A password so that the default trust authentication mode is not used;" https://www.postgresql.org/docs/current/creating-cluster.html Shouldn't we change that to "-A scram-sha-256" ? Regards Daniel