Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
postgresql-common
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
PostgreSQL
postgresql-common
Commits
c1e61705
Commit
c1e61705
authored
1 year ago
by
Michael Banck
Browse files
Options
Downloads
Patches
Plain Diff
pg_createcluster: Do not remove existing data directory on failure. (Closes: #105630)
parent
b16caf2c
No related branches found
No related tags found
1 merge request
!19
pg_createcluster: Do not remove existing data directory on failure. (Closes: #105630)
Pipeline
#620668
passed
1 year ago
Stage: provisioning
Stage: build
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
pg_createcluster
+2
-0
2 additions, 0 deletions
pg_createcluster
with
2 additions
and
0 deletions
pg_createcluster
+
2
−
0
View file @
c1e61705
...
...
@@ -361,6 +361,8 @@ if (-f "$datadir/PG_VERSION") {
(
$owneruid
,
$ownergid
)
=
(
stat
"
$datadir
/PG_VERSION
")[
4
,
5
];
if
(
$existingver
==
$version
)
{
print
"
Configuring already existing cluster (configuration:
$confdir
, data:
$datadir
, owner:
$owneruid
:
$ownergid
)
\n
";
# Do not remove already existing data directory on errors
$cleanup_cruft
=
0
;
}
else
{
error
"
$datadir
contains a version
$existingver
cluster, but
$version
was requested
";
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment