so processed 282 unsubscriptions from
> people who managed to read and work with the instructions.
Maybe we need an "unsubscribe" email list. ;-)
--
Bruce Momjian <br...@momjian.us>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 +
ent from any other
> 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 <br...@momjian.us>http://momjian.us
EnterpriseDB http:/
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
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 http://enterprisedb.co
A bit of digging in the git history says that the check was added here:
> >
> > commit 453d74b99c9ba6e5e75d214b0d7bec13553ded89
> > Author: Bruce Momjian <br...@momjian.us>
> > Date: Fri Jun 10 03:02:30 2005 +
> >
> >
completes, rather than when it starts, which is what
log_statement does.
And, yes, using %c to match up lines will work too.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are
pgrade_utility.log"
> 2>&
> 1
>
> *failure*
> "c:\EMC\AppSync\jboss\datastore_96\engine\bin/pg_ctl" -w -D
> "c:\EMC\AppSync
> \jboss\datastore_96\data" -o "" -m fast stop >> "pg_upgrade_utility.log&q
utilities 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.
--
Bruce Momj
h, 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 +
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 bad n
n 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 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 somewhere as
; > 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
store data 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 http://
emoval 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 +
+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.us
EnterpriseDB
ave
> 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 +
tion, 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://momjian.us
Enterpris
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 +
very possibly related.
> 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 <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
og.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 <br...@momjian.us>http://momjian.us
EnterpriseDB htt
On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
> Bruce Momjian <br...@momjian.us> 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
> up
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
EnterpriseDB
items
were added 18 months ago:
https://wiki.postgresql.org/index.php?title=Code_of_Conduct=31924=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
"protected groups" concept because it is
all 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
er initialized correctly, so perhaps you messed up
> > something in your environment?
> > --
> > Michael
>
>
>
> Problem caused by my eyesight.
> A colleague pointed out the typo in the argument to the -d parameter.
> Working as int
is setup sr again...
The pg_upgrade docs explain how to upgrade standby servers. You can use
--link option for that even if you didn't use link option to upgrade the
primary.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you
h 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 perfect.
--
Bruce M
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
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
mit'? That is not a client-supplied command
and is not tracked, and I am not sure we would want to do that.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+
w it is for now.
There was too much concern that users would accidentally start the old
server at some later point, and its files would be hard linked to the
new live server, leading to disaster.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprised
On Thu, Feb 21, 2019 at 09:31:32PM -0500, Stephen Frost wrote:
> Greetings,
>
> * Bruce Momjian (br...@momjian.us) wrote:
> > On Tue, Feb 19, 2019 at 12:25:24PM -0500, Stephen Frost wrote:
> > > Ah, right, I forgot that it did that, fair enough.
> > >
ame encoding, connection limit (if
> anything was specified), etc. Is there a way to create this DDL?
pg_dump --schema-only maybe?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I.
nterfaces not built using
libpq, e.g. JDBC.
--
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 +
UI tools don't
> know what to do if they get an error just listing the databases). Also it is
> so piecemeal I wouldn't trust that I'd blocked off all avenues of getting
> the information.
>
> I'd love to be corrected on this btw if anyone has better information! :-)
Heroku had that
-|
> 2019-01-31 | 2019-02-03
> (1 row)
Uh, this worked:
SELECT date_trunc('week', CURRENT_TIMESTAMP) + '6 days';
?column?
2019-02-03 00:00:00-05
--
Bruce Momjian http://momjian.us
Enterp
On Thu, Jan 31, 2019 at 02:21:52PM -0600, Ron wrote:
> On 1/31/19 2:15 PM, Bruce Momjian wrote:
> >On Thu, Jan 31, 2019 at 02:11:14PM -0600, Ron wrote:
> >>Hi,
> >>
> >>v9.6.6
> >>
> >>Is there a built in function to calculate, for example
module?
Uh, oracle_fwd uses a kernel module? Are you sure? That is surprising.
--
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 +
//momjian.us/main/blogs/pgblog/2019.html#February_25_2019
Here is discussion about adding a GUC to set the old behavior, but was
rejected:
https://www.postgresql.org/message-id/flat/01d4caed%24d29b9ae0%2477d2d0a0%24%40pcorp.us
--
Bruce Momjian http://momjian.us
Enterpr
VACUUM FULL is not
> releasing space in there.
>
> Is there any way how to check if anything in that folder is really not used
> anymore and consider that safe to delete?
>
> I'll appreciate any suggestions.
They is an output line of pg_upgrade which says:
Running this script wi
did blog posts about lockin and vendor selection strategy that might
help:
https://momjian.us/main/blogs/pgblog/2019.html#March_5_2019
https://momjian.us/main/blogs/pgblog/2019.html#March_7_2019
--
Bruce Momjian http://momjian.us
EnterpriseDB
The Postgres COPY format is very reliable and able to dump/reload _any_
data sequence. Many commercial data dump implementations are simpler
but are not able to be as reliable.
The bottom line is that you are going to need to double the backslashes
unless you move to CSV mo
On Fri, May 3, 2019 at 10:04:44AM -0400, Bruce Momjian wrote:
> On thing the original poster might be missing is that the copy DELIMITER
> is used between fields, while backslash is used as an escape before a
> single character. While it might be tempting to try to redefine the
> I'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 nice. :-)
--
Bruce Mo
o outline all the steps necessary. This is not
for the faint of heart. ;-)
--
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 +
ng
> > changes in v12 especially changes to default behavior like this? Will there
> > be a new cte_collapse_limit setting or similar?
>
> Check the release notes.
Yes, once they are written in a few weeks.
--
Bruce Momjian http://momjian.us
EnterpriseDB
);
>
>
> Unfortunately, the query above does not work.
I had to do this one and put the EXPLAIN in a function and then called
the function and captured the output, see this and following slides:
http://momjian.us/main/writings/pgsql/optimizer.pdf#page=11
--
Bruce Momjian
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:
>
>
ypt
\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 gpg2 options will allow it to match?
Thanks.
--
Bruce Momjian h
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
uot;
" 'regproc', "
" 'regprocedure' "
/* regrole.oid is preserved, so 'regrole' is OK */
/* regtype.oid is preserved, so 'regtype' is OK */
" ) AND "
" c.relnamespace =
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 a
igger-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 ht
o 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 +
tual 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 +
ied 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
ere, 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://enterprisedb.com
+ As you
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 +
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.
>
y 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 dir
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
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
>
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
>
to a 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
lass 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://enterprisedb.com
The u
poses, 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 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
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 Goo
g 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.html#June_26_2020
--
Bruce
database 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
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
the 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
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
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 hard.
--
Bruce Momji
er/switch-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
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,
>
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
'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 https://momjian.us
t 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 perspective.
You also h
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
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
nteract 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 https:/
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
> 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
ts 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://momjian.
f
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
EnterpriseDB
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 negatives.
--
B
ptimization 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 https:
;
>
> 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.us
E
g 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
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
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
tps://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
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
ggest 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
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 tabl
would 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 htt
1 - 100 of 243 matches
Mail list logo
