.
> I'm glad that the storm is behind you guys now.
Yes, a weather-related power outage was the cause of the 48-hour
downtime. Sorry.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
UPDATE pg_catalog.pg_class
SET relfrozenxid = '558', relminmxid = '1'
WHERE oid = 'public.test'::pg_catalog.regclass;
Is it possible that pg_upgrade used 50M xids while upgrading?
--
Bruce Momjian http://momjian.us
Enterpri
On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
> Bruce Momjian writes:
> > Is it possible that pg_upgrade used 50M xids while upgrading?
>
> Hi Bruce.
>
> Don't think so, as I did just snap the safety snap and ran another
> upgrade on that.
>
&g
On Wed, Apr 4, 2018 at 08:29:06PM -0400, Bruce Momjian wrote:
> On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
> > Bruce Momjian writes:
> > > Is it possible that pg_upgrade used 50M xids while upgrading?
> >
> > Hi Bruce.
> >
> > Don
; file system).
Uh, at the risk of asking an obvious question, why is the WAL file COW
if it was renamed? No one has the old WAL file open, as far as I know.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
PostgreSQL server?
>
>Is there the equivalent of Oracle "wallet" ?
Late reply, but the last presentation on this page shows how to use
cryptographic hardware with Postgres:
https://momjian.us/main/presentations/security.html
You could modify that to use a key management
certainly see considering it, but if
it's not a lot of effort then I'd say it's definitely worth it.
so the rule I have been using for backpatching doc stuff has changed
recently.
--
Bruce Momjian http://momjian.us
EnterpriseDB
ik Fearing +33 6 46 75 15 36
> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
>
>
>
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
--
Bruce Momjian http://momjian.
version would have
> to be done on the client side.
Wow, I am kind of surprised by that. Do any other data types have this
behavior?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
t's a very good solution, IMHO.
>
> Otherwise, WxWidgets (https://www.wxwidgets.org/) could also be a good
> solution...
PGAdmin used to use WxWidgets but left it recently for PGAdmin 4. I
would ask them what problems caused them to stop using it.
--
Bruce Momjian http
es to get the job done. This is an area the
docs don't cover well, but our blogs and wikis do.
For #3, this is mostly covered by books. This topic requires a lot of
explanation and high-level thinking. We have some of that in our docs,
but in general books probably do this better.
--
s.
Uh, who is building PL/v8 currently, and for what operating systems? No one?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
lf can force
serialized data access, slowing things down.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Fri, Aug 10, 2018 at 09:41:44PM +0200, Christoph Berg wrote:
> Re: Bruce Momjian 2018-08-10 <20180810192205.gc7...@momjian.us>
> > Uh, who is building PL/v8 currently, and for what operating systems? No
> > one?
>
> No one is likely correct.
Wow, OK. That's
a encrypted in a
database only if it is a payload on another piece of non-encrypted data.
You can't easily index, restrict, or join encrypted data, so it doesn't
have a huge value alone in a database.
--
Bruce Momjian http://momjian.us
EnterpriseDB
DBA removal of data
is secure auditing --- I should have mentioned that.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Tue, Aug 14, 2018 at 03:59:19PM -0400, Bruce Momjian wrote:
> On Fri, Aug 10, 2018 at 04:06:40PM -0400, Benedict Holland wrote:
> > I also would take Bruce's comment with a massive grain of salt. Everything
> > that
> > everyone does on a database is logged somewhe
; > July 1 2018.
>
> We seem to be a bit past that timeline... Do we have any update on when
> this will be moving forward?
>
> Or did I miss something?
Are we waiting for the conference community guidlines to be solidified?
--
Bruce Momjian http://momjian.us
Ent
acces function call, e.g.
SELECT lower(public.unaccent(btrim(regexp_replace(
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
at all about how such problems were handled, or not handled.
There is a risk that if we adopt a CoC, and nothing happens, and the
committee does nothing, that they will feel like a failure, and get
involved when it was best they did nothing. I think the CoC tries to
address that, but nothing is per
On Sat, Sep 15, 2018 at 11:32:06AM -0400, Bruce Momjian wrote:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> addre
considerate, and if you
> can’t be nice, be at least civil”.
I have to admit I am surprised how polite the language is here,
considering how crudely some other open source projects communicate.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://e
and those example items
were added 18 months ago:
https://wiki.postgresql.org/index.php?title=Code_of_Conduct&diff=31924&oldid=29402
I realize that putting no examples has its attractions, but some felt
that having examples would be helpful. I am not a big fan of the
"pr
be prohibited."
>
> The inclusion of "political or any other opinion" is a nice addition and
> prevents a lot of concern.
Huh. Certainly something to consider when we review the CoC in a year.
--
Bruce Momjian http://momjian.us
EnterpriseDB
or both.
Yes, I had the same reaction. Activity not involving other Postgres
members seems like it would not be covered by the CoC, except for
"behavior that may bring the PostgreSQL project into disrepute", which
seems like a stretch.
--
Bruce Momjian http://momjian.us
E
'd like to DRY them up so there aren't two lists which confuses
> newcomers. Any objections? If not I'll probably make one of those
> pages into GUI's and one into "non GUI's" or something like that.
Agreed, a cleanup would be n
pgp_sym_encrypt
\xc30d0409030282dbcc61c149fd4b67d24...
I realize the \x is from the bytea output function, but the hex digits
don't match, and the gpg2 output is slightly longer than the
pgp_sym_encrypt() output. What g
On Tue, Aug 27, 2019 at 02:05:28PM -0400, Jeff Janes wrote:
> On Tue, Aug 27, 2019 at 1:33 PM Bruce Momjian wrote:
>
> I am trying to generate output from the command-line program gpg2 that
> matches the output of pgp_sym_encrypt(). gpg2 outputs:
>
>
chema, and those are what is
complaining about. (The pg_upgrade query specifically skips checking
pg_catalog tables.)
I think maybe pg_upgrade should always output the schema name for such
objects --- I think someone propsed a patch for that recently.
--
Bruce Momjian http://momjian.us
Enter
perator', "
" 'regproc', "
" 'regprocedure' "
/* regrole.oid is preserved, so 'regrole' is OK */
/* regtype.oid is preserved, so 'regtype' is OK */
Allowing REINDEX to fix things is
the best of both worlds --- fast upgrades, and after some REINDEX-ing,
faster Postgres.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
r-matrix.html>.
> The ddl_command_end is issued, and the function is invoked, but
> pg_event_trigger_ddl_commands() returns NULL on such invocation
> because sql_drop is the event with the attached data.
Do the Postgres docs need improvement here?
--
Bruce Momjian
e non-row information, then use
streaming replication with logical decoding to get the rows for each
transaction started by the user.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so yo
astic IP address here, instead I have
> created a network load balancer in AWS, created a target group with all the
> three pgpool nodes as targets).
>
> Regards,
> Venkatesh.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpr
dates for database
> objects.
>
>
>
> Is this something that has been considered for implementation?
I wrote a blog about this:
https://momjian.us/main/blogs/pgblog/2017.html#November_21_2017
--
Bruce Momjian http://momjian.us
EnterpriseDB
responds with an ErrorResponse. The
actual PasswordMessage can be computed in SQL as concat('md5',
--> md5(concat(md5(concat(password, username)), random-salt))). (Keep in
mind the md5() function returns its result as a hex string.)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
V8 is packaged), which has decreased PL/V8
adoption.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Thu, Mar 26, 2020 at 10:07:48AM +0300, Ivan Panchenko wrote:
>
> On 26.03.2020 03:50, Bruce Momjian wrote:
> > On Wed, Mar 25, 2020 at 05:46:27PM +0200, Marius Andreiana wrote:
> > > Thanks Tom, that makes sense. Appreciate your time to explain the context.
> >
k we wanted more ability to change an existing cluster
before doing that since it would affect pg_upgraded servers.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
nually created c extension
> functions. I can't just move them to /usr/pgsql-11/lib/ because they we
> compiled with PostgresSQL10 and not 11.
>
> How can I resolve this issue? How can I delete them properly if porting them
> to 11 is a painful process? Deleting them d
re gets compromised, the data
> cannot be read. However, if your key is also in the store, then when
> your compromised, your key is compromised and your encryption becomes a
> mute issue.
This blog entry illustrates row signing on the client side:
https://mom
the low-level stuff
rarely changes, so once you understand it, you can use it forever. The
big problem is getting people to see the value in learning that stuff
when they don't have an immediate need --- curiosity helps with
motivation. :-)
--
Bruce Momjian https://momjian.us
ful optimization work in order to make it faster. Not a
> weekend job, I'm afraid :-(
FYI, we never actually found what version of pg_dump was being used,
since pg_upgrade uses the pg_dump version in the newer cluster. We only
know the user is coming _from_ 9.3.
--
Bruce Momjian htt
ing you can only use pg_upgrade 11.X to upgrade _to_ Postgres
11.X. If you want to upgrade to 12, you have to use pg_upgrade from 12.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
t; on it, but there are things other RDBMS-vendors do better...
The bigger issue is that while we _could_ do this, it would add more
problems and complexity, and ultimately, I think would make the
software less usable overall and would be a net-negative. We know of no
way to do it without a ton of
; >
>
> Plus PG does not directly support cross database queries using 3 part name,
> something
> sqlserver excels at.
We consider the lack of this ability to be a security benefit.
Cross-container queries can be done using schemas.
--
Bruce Momjian https://momjian.u
On Sat, Jun 13, 2020 at 05:06:37PM -0500, Ron wrote:
> On 6/13/20 1:46 PM, Bruce Momjian wrote:
> > On Wed, Jun 3, 2020 at 08:53:45PM +0200, Andreas Joseph Krogh wrote:
> > > I agree these are all technical issues, but nevertheless - "implementation
> > > detai
On Sat, Jun 13, 2020 at 09:27:25PM -0400, Bruce Momjian wrote:
> On Sat, Jun 13, 2020 at 05:06:37PM -0500, Ron wrote:
> > On 6/13/20 1:46 PM, Bruce Momjian wrote:
> > > On Wed, Jun 3, 2020 at 08:53:45PM +0200, Andreas Joseph Krogh wrote:
> > > > I agree these
t, leading to misestimation and wrong
plans. If the new EXPLAIN ANALYZE has estimates closer to actual, the
problem should not reappear.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
lude 'some_file' in the new
> postgresql.conf and you are good.
Yes, the community instructions require you to reconfigure the new
server to match the old one. Some packagers who automate pg_upgrade
might do that configuration migration automatically.
--
Bruce Momjian http
w users to disable it if they want and
> clearly document that option as insecure. I also suspect that without
> the ability to somehow disable the checks, people will find elaborate
> ways to work around them which are almost certainly going to be even
> worse from a security persp
ns could interact with indexes
> in such a manner.
This blog entry explains how statistics on expression/function indexes
can help:
https://momjian.us/main/blogs/pgblog/2017.html#February_20_2017
--
Bruce Momjian https://momjian.us
EnterpriseDB
word?
>
> And that the OP is indeed using the 'postgres' user and not the ' postgres'
> user (as she wrote in the subject).
Uh, how are those different?
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
O%3D8N%3Dnc2xVZPB0d9e-VjJ%3DYaRnw%40mail.gmail.com
>
>
>
>
> However, I am not sure how to apply this patch and I had the
> following questions:
>
> 1. We are using PostGreSQL 12. Is it possible to apply patches on top of
> existing
oblem with space.
>
> The error says you do.
> Where is pg_logical/snapshots/ mounted?
> Are there specific restrictions on that mount?
I would also look at your kernel log.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
On Tue, Jun 30, 2020 at 10:03:52PM +0100, FOUTE K. Jaurès wrote:
> Le mar. 30 juin 2020 à 21:23, Bruce Momjian a écrit :
>
> On Tue, Jun 30, 2020 at 01:16:58PM -0700, Adrian Klaver wrote:
> > On 6/30/20 11:03 AM, FOUTE K. Jaurès wrote:
> > > Hi everyone,
>
https://www.postgresql.org/message-id/flat/CAAJ_b96Gupt_LFL7uNyy3c50-wbhA68NUjiK5%3DrF6_w%3Dpq_T%3DQ%40mail.gmail.com
so, yes, it is possible, but no one has implemented it. This is the
first complaint I have heard about this.
--
Bruce Momjian https://momjian.us
EnterpriseDB
ame tuple serialize.
You might want to look at this:
https://momjian.us/main/presentations/internals.html#mvcc
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
into a postgres v9.6 database work and be
> officially supported?
Yes, you can always use a newer pg_dump on an older database, though the
reverse is not recommended. In fact, if you are upgrading to PG 12, it
is recommended to use pg_dump v12 to dump a Postgres database from an
earl
g_restore that
you are loading _into_, not what you dumped from.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
itch-back too, but you have
to manage session migration. I wrote a blog about it:
https://momjian.us/main/blogs/pgblog/2018.html#October_1_2018
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup i
larger
> cluster that is running 64 bit. Should there be something special done in
> order
> to accommodate the difference?
How is the data sent? In almost every case, the translation should work
fine. I think 32-bit overflow should be your only concern here.
--
Bruce Momji
64-bit going above the
32-bit range. As long as everything stays < 32-bits, you should be
fine. We don't transfer binary values very often.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
On Mon, Aug 31, 2020 at 10:14:48PM +, Godfrin, Philippe E wrote:
> Fabulous, thanks much.
You still have not told us how you are transfering the data, so we can
be sure.
---
>
> From: Bruce Momjian
>
query results
as binary, but it is technically possible with binary COPY or triggers.
---
>
> pg
>
>
>
> From: Bruce Momjian
> Sent: Monday, August 31, 2020 5:19 PM
> To: Godfrin, Philippe E
>
appear to be invalidly
> encoded.
I think the issue is that role and database names are controlled by
privileged users, while application_name is not.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
f explaining your issues. I think the
underlying problem is that Postgres is targeting a wide market, and your
use-case for a more limited or self-contained database doesn't fit many
of those markets. Also, PostGIS is one of the most complex extensions,
so adding simpler ones should not be as
lname FROM pg_class LIMIT 2;
ctid | relname
+--
(0,46) | pg_statistic
(0,47) | pg_type
The format is page number, item number on page.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprise
On Sun, Sep 20, 2020 at 01:15:26PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Mon, Sep 14, 2020 at 05:39:57PM -0400, Tom Lane wrote:
> >> On the other hand, the very same thing could be said of database names
> >> and role names, yet we have never worried mu
ding the docs,
particularly for performance purposes, must have an existing knowledge
of a lot of low-level things --- this could be the cause of your
frustration.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
On Thu, Sep 24, 2020 at 11:47:10PM -0500, Ron wrote:
> On 9/24/20 6:20 PM, Bruce Momjian wrote:
> > On Wed, Sep 23, 2020 at 12:28:14AM +0200, tutilu...@tutanota.com wrote:
> > > Sep 21, 2020, 7:53 PM by j...@commandprompt.com:
> > > See my comment about Google. T
d really see a benefit in doing so.
>
> It has especially been discussed to implement a behaviour that complies
> with the SQL standard which *requires* to fold non-quoted names to uppercase!
I did write a blog entry about case folding:
https://momjian.us/main/blogs/pgblog/2020.h
base is
> apparently idle then dropping the database and doing the restore. Then
> restarting the daemons etc. I am sure I am not doing this the right way so
> advice gratefully received.
I would modify pg_hba.conf to block access temporarily.
--
Bruce Momjian
e v10 database:
>
> revoke select on pg_catalog.pg_pltemplate from appuser;
Yeah, there must be a reference to pg_catalog.pg_pltemplate somewhere
that was missed. I think a simple dump/restore would also error on the
restore, but a normal restore might ignore the error, while pg_upgrade
will n
SELECT ON TABLE “pg_catalog"."pg_pltemplate” TO "appuser”;
>
> Which points to the dangers of doing things to the system tables. They can
> change/disappear between major versions.
And pg_dump (used by pg_upgrade) had little handling for such changes.
--
Bruce Mom
ly clearer and better along
> exactly the same lines.
I think it is funny that the Redit thread thinks we made the format
change because of mobile, but it was actually more for PDF output, which
is more old-school than even web pages.
--
Bruce Momjian https://momjian.us
EnterpriseD
/hOgMwmFYJM4
The URL was listed on the web page of the obituary:
https://www.arbormemorial.ca/capital/obituaries/christopher-bruce-browne/57436/
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
n i can wait otherwise i have to move towards Client Side
> encryption as you mentioned.
Postgres shared the same WAL files for all databases in a cluster, so
the idea of having multiple keys for different users is very hard or
impossible to implement. Client-side is much better for this use
braries. Also, try
running this query and show us what is not the default:
SELECT name, current_setting(name), source
FROM pg_settings
WHERE source NOT IN ('default', 'override');
--
Bruce Momjian https://momjian.us
EnterpriseDB
urns true if the raster is empty
> (width = 0 and height = 0). Otherwise, returns false.’;
My guess is that this is a crash in the PostGIS shared library. I would
ask the PostGIS team if they know of any crash cases, and if not, I
think you need to do a pg_dump of the database and te
On Tue, Nov 17, 2020 at 02:44:47PM -0500, Bruce Momjian wrote:
> On Tue, Nov 17, 2020 at 11:59:10AM -0500, Jeremy Wilson wrote:
> > pg_restore: WARNING: terminating connection because of crash of another
> > server process
> > DETAIL: The postmaster has commanded this s
--
>
> BINGO! after drops all went smooth and easy
I think one big problem is that when pg_upgrade fails in this way, users
are required to do some complex system catalog queries to diagnose the
cause. Is there a way to simplify this for them?
--
Bruce Momjian https:
On Wed, Nov 18, 2020 at 03:25:56PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > I think one big problem is that when pg_upgrade fails in this way, users
> > are required to do some complex system catalog queries to diagnose the
> > cause. Is there a way to s
reports affected databases to the
* user and explains how to remove them. 8.1 git commit:
* e0dedd0559f005d60c69c9772163e69c204bac69
* http://archives.postgresql.org/pgsql-hackers/2012-03/msg01101.php
* http://archives.postgresql.org/pgsql-bugs/2012-05/msg00206.p
eports affected databases to the
> > * user and explains how to remove them. 8.1 git commit:
> > * e0dedd0559f005d60c69c9772163e69c204bac69
> > * http://archives.postgresql.org/pgsql-hackers/2012-03/msg01101.php
> > * http://archives.post
"\n"
> > "in each affected database:\n"
> > "\n");
> >}
> >pg_log(PG_WARNING, "%s\n", active_db->db_name);
> >
tore, without --create, no longer dump/restore
> database-level comments and security labels; those are now treated as
> properties of the database."
Yeah, I realize this new behavior is kind of odd, but logically, it
makes sense.
--
Bruce Momjian https://momjian.us
?
This blog entry summarizes the various levels of isolation and their
benefits:
https://momjian.us/main/blogs/pgblog/2012.html#April_23_2012
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in it
ould be to VACUUM (FREEZE) these static table once, then autovacuum
> won't ever perform resource consuming activities on them again.
Yes, also, even if you never do that, autovacuum will eventually freeze
those tables and never access them again.
--
Bruce Momjian
gle.com/site/robertmhaas/presentations
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
On Sun, Jan 3, 2021 at 05:37:52PM +, Thomas Flatley wrote:
> Excellent - thanks for the fast response - it was an oracle dba that set it
> up initially so that may explain it -
Agreed. It was probably done that way for an invalid reason and should
be cleaned up.
--
Bruce M
I do with old tablespaces when upgrading ?
There should be a subdirectory under your tablespace directory for every
major version, e.g., PG_13_202007201. I have no idea why your _new_
version already has a directory there. Do you have a second cluster on
the machine that is using that
I suggest you do more research than just run that --- at least I would.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
thers the same. Same with not quoting entire
> messages on reply.
That "quoting entire messages on reply" is something I see far too often
here. I have been meaning to mention this problem. Thousands of people
are reading postings here, so it pays to take time to trim down what
others
On Sat, Jan 16, 2021 at 03:34:32PM -0500, Tom Lane wrote:
> Alvaro Herrera writes:
> > On 2021-Jan-16, Bruce Momjian wrote:
> >> That "quoting entire messages on reply" is something I see far too often
> >> here. I have been meaning to mention this problem.
postgresql-10-setup to create NEW empty base (in
> /var/lib/pgsql/ or somewhere, for -D option),
> 3). do pg_upgrade.
>
> Is that correct?
>
> Is there somewhere "guide for 9.x -> 10.x CONCEPTS changes (and upgrade)
> guide"? (clusters etc).
The pg_upgade docs have all the steps.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
On Mon, Jan 18, 2021 at 03:13:13PM -0600, Ron wrote:
> On 1/18/21 2:58 PM, Bruce Momjian wrote:
> > On Mon, Jan 18, 2021 at 09:53:33PM +0100, W.P. wrote:
> [snip]
> > > Ok, so "step-by-step":
> > > 1), I copy / move "somewhere" OLD DB files (
to host the old and new clusters simultaneously during the migration
> process.
pg_upgrade docs have instructions on how to upgrade replicas in place
using rsync with hard links.
--
Bruce Momjian https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
used for people who post looking for jobs.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
houldn't and files from 11/main and 12/main
> will all be under 12/main, I just have doubts.
>
> Is there an easy way to tidy this up?
Yes, if the sizes made sense, removing 11 would be fine, but right now,
it doesn't sound right.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
1 - 100 of 259 matches
Mail list logo
