Hi Stephen,
> On 22. Jun, 2020, at 07:36, Stephen Frost wrote:
> That's not the only case that I, at least, have heard of- folks aren't
> really very happy with their backups fail when they could have just as
> well completed, even if they're overlapping. Sure, it's better if
> backups are sched
Greetings,
* Paul Förster (paul.foers...@gmail.com) wrote:
> > On 21. Jun, 2020, at 21:35, Magnus Hagander wrote:
> > One not uncommon case is for example being able to provision a new replica
> > while a backup is running. Since replicas are provisioned starting off a
> > base backup, being ab
Hi Magnus,
> On 21. Jun, 2020, at 21:35, Magnus Hagander wrote:
> One not uncommon case is for example being able to provision a new replica
> while a backup is running. Since replicas are provisioned starting off a base
> backup, being able to run that concurrently is very useful. Especially i
Laurenz Albe wrote:
> On Mon, 2020-06-22 at 09:44 +1000, raf wrote:
> > A superuser can access files and start programs on the server machine.
> > > A dedicated superuser may for example attach to PostgreSQL with a debugger
> > > and read the value of the variable.
> > >
> > > And if that doesn't
I have a table with the schema:
CREATE TABLE fluent (id BIGSERIAL, record JSONB);
Then I created a couple of indexes:
1) CREATE INDEX idx_records ON fluent USING GIN (record);
2) CREATE INDEX idx_btree_records ON fluent USING BTREE ((record ->>
'destinationServiceName'));
Now, if I run a query t
On Mon, Jun 22, 2020 at 12:25 AM Peter J. Holzer wrote:
> I've read http://jepsen.io/analyses/postgresql-12.3 which reports a
> problem in PostgreSQL's SERIALIZABLE isolation leven (which has since been
> fixed) and also shows an example of a violation of what they consider to
> be the correct def
On Mon, 2020-06-22 at 09:44 +1000, raf wrote:
> A superuser can access files and start programs on the server machine.
> > A dedicated superuser may for example attach to PostgreSQL with a debugger
> > and read the value of the variable.
> >
> > And if that doesn't work, there may be other things
On Mon, 2020-06-22 at 14:16 +1200, Guy Burgess wrote:
> I've seen some situations where it would be very handy if PostgreSQL
> could automatically prefix column names in a SELECT query with their
> table names (or its alias). So for two tables, a & b, each with
> columns "id" and "title":
>
>
Hello,
I've seen some situations where it would be very handy if PostgreSQL
could automatically prefix column names in a SELECT query with their
table names (or its alias). So for two tables, a & b, each with
columns "id" and "title":
SELECT * FROM a , b;
instead of returning ambiguou
Laurenz Albe wrote:
> On Wed, 2020-06-17 at 13:23 -0700, Michel Pelletier wrote:
> > In my extension pgsodium I'm defining a custom variable at startup to store
> > a key:
> >
> > https://github.com/michelp/pgsodium/blob/master/src/pgsodium.c#L1107
> >
> > I'm using the flags GUC_NO_SHOW_ALL |
On 6/21/20 10:45 AM, Peter J. Holzer wrote:
On 2020-06-21 10:32:16 -0500, Ron wrote:
On 6/21/20 8:28 AM, Peter J. Holzer wrote:
To make a full backup with the "new" (non-exclusive) API, a software
must do the following
1. open a connection to the database
2. invoke pg_start_backup('label', fa
On Sat, Jun 20, 2020 at 9:04 AM Paul Förster
wrote:
> Hi Stephen,
>
> > On 19. Jun, 2020, at 18:02, Stephen Frost wrote:
> > When it comes to 'backup mode', it's actually the case that there can be
> > multiple backups running concurrently because there isn't actually a
> > single 'cluster wide
On 6/21/20 7:53 AM, Vishal Agrawal wrote:
Seenu, I don't see any journalctl entry other than the log that
postmaster has been killed. (Jun 21 14:52:30 f9cbc3b08e20 systemd[1]:
postgresql-12.service: Killing process 1096 (postmaster) with signal
SIGKILL.)
Any further suggestions on where to loo
On Sun, Jun 21, 2020, 8:23 PM Vishal Agrawal
wrote:
> Seenu, I don't see any journalctl entry other than the log that postmaster
> has been killed. (Jun 21 14:52:30 f9cbc3b08e20 systemd[1]:
> postgresql-12.service: Killing process 1096 (postmaster) with signal
> SIGKILL.)
> Any further suggestion
On 2020-06-21 10:32:16 -0500, Ron wrote:
> On 6/21/20 8:28 AM, Peter J. Holzer wrote:
> > To make a full backup with the "new" (non-exclusive) API, a software
> > must do the following
> >
> > 1. open a connection to the database
> >
> > 2. invoke pg_start_backup('label', false, false) in the con
Peter,
I don't understand that last step "5. copy the result from the previous step
to the backup medium." It seems to be a duplication of "3. copy the
contents of the data directory to the backup medium".
On 6/21/20 8:28 AM, Peter J. Holzer wrote:
This is inspired by the thread with the su
Seenu, I don't see any journalctl entry other than the log that postmaster
has been killed. (Jun 21 14:52:30 f9cbc3b08e20 systemd[1]:
postgresql-12.service: Killing process 1096 (postmaster) with signal
SIGKILL.)
Any further suggestions on where to look ?
It does seem to work with systemd-239-18 (
This is inspired by the thread with the subject "Something else about
Redo Logs disappearing", but since that thread is already quite long,
since I have lost track what exactly "Peter"'s problem is and since his
somewhat belligerent tone makes it unappealing to reread the whole
thread I'll attempt
I've read http://jepsen.io/analyses/postgresql-12.3 which reports a
problem in PostgreSQL's SERIALIZABLE isolation leven (which has since been
fixed) and also shows an example of a violation of what they consider to
be the correct definition of REPEATABLE READ.
Specifically:
T1: r 190 [1 2] |
On Sun, Jun 21, 2020, 8:57 AM Vishal Agrawal
wrote:
> Hello,
>
> I'm trying to install postgresql 12 on CentOS 8.2 as following -
>
> First I run docker container on the host -
> # docker run --privileged -dit --name pgdg centos:8.2.2004 /sbin/init
>
> Then inside the container, I run the comman
20 matches
Mail list logo
