1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
//! Lifecycle guard for a running `PostgreSQL` cluster.
//!
//! [`ClusterGuard`] manages the non-`Send` components of a cluster's lifecycle:
//! environment variable restoration and cluster shutdown. It is intentionally
//! `!Send` to ensure environment guards are dropped on the thread that created
//! them.
//!
//! # Architecture
//!
//! The guard holds:
//! - **Environment guards**: `ScopedEnv` instances that restore environment variables when dropped
//! - **Shutdown resources**: Runtime, `PostgreSQL` instance, and configuration needed to cleanly
//! stop the cluster
//! - **Tracing span**: Keeps the cluster's observability span alive
//!
//! # Drop Behaviour
//!
//! When dropped, the guard:
//! 1. Stops the `PostgreSQL` cluster (gracefully if possible)
//! 2. Restores environment variables to their pre-cluster state
//!
//! # Thread Safety
//!
//! `ClusterGuard` is intentionally `!Send` because `ScopedEnv` uses thread-local
//! storage to track environment changes. Dropping on a different thread would
//! corrupt the environment restoration logic.
//!
//! # Testing
//!
//! `ClusterGuard`'s shutdown and environment-restoration behaviour is tested
//! in `tests/cluster_split_constructors.rs`:
//!
//! - `new_split_creates_working_handle_and_guard`: Verifies that dropping the guard stops the
//! `PostgreSQL` cluster (`postmaster.pid` is removed) and restores environment variables to their
//! pre-cluster state.
//!
//! - `start_async_split_creates_working_handle_and_guard`: Tests the async variant with the same
//! shutdown and restoration assertions.
use PostgreSQL;
use ;
use ;
use crate::;
/// Lifecycle guard for a running `PostgreSQL` cluster.
///
/// This guard manages cluster shutdown and environment restoration. It is
/// intentionally `!Send` to ensure thread-local environment state is handled
/// correctly.
///
/// # Obtaining a Guard
///
/// Use [`TestCluster::new_split()`](super::TestCluster::new_split) to obtain
/// a handle and guard pair:
///
/// ```no_run
/// use pg_embedded_setup_unpriv::TestCluster;
///
/// let (handle, guard) = TestCluster::new_split()?;
/// // handle: ClusterHandle (Send + Sync)
/// // guard: ClusterGuard (!Send, manages lifecycle)
///
/// // When guard drops, cluster shuts down and environment is restored
/// # Ok::<(), pg_embedded_setup_unpriv::BootstrapError>(())
/// ```
///
/// # Shared Cluster Pattern
///
/// For shared clusters that should run for the entire process lifetime,
/// the guard must be explicitly forgotten to prevent shutdown on drop.
/// Use [`std::mem::forget`] to keep the cluster running, and register
/// the shutdown hook so the postmaster is stopped on process exit:
///
/// ```no_run
/// use std::sync::OnceLock;
///
/// use pg_embedded_setup_unpriv::{ClusterHandle, TestCluster};
///
/// static SHARED: OnceLock<ClusterHandle> = OnceLock::new();
///
/// fn shared_handle() -> &'static ClusterHandle {
/// SHARED.get_or_init(|| {
/// let (handle, guard) = TestCluster::new_split().expect("cluster bootstrap failed");
/// handle
/// .register_shutdown_on_exit()
/// .expect("shutdown hook registration failed");
/// std::mem::forget(guard);
/// handle
/// })
/// }
/// ```
///
/// **Warning**: Dropping the guard shuts down the cluster. Do not use the
/// handle after the guard has been dropped unless the guard was forgotten.
// Note: ClusterGuard is !Send because it contains ScopedEnv which has
// PhantomData<Rc<()>>. This is verified by the test in tests/test_cluster.rs
// which uses a compile_fail doctest to ensure the type cannot be sent across
// threads.