Hi there,
I saw there was a question about a similar topic recently but my use case
is quite different so there may be a different answer.
Roughly, I have a database which is updated by a single stream of updates
(through jdbc), so I have a single write transaction at any time. However,
sometimes
Hello Marc-Antoine,
On Thu, 2018-03-15 at 10:43 +0100, Marc-Antoine Nüssli wrote:
> Hi there,
>
> I saw there was a question about a similar topic recently but my use
> case is quite different so there may be a different answer.
> Roughly, I have a database which is updated by a single stream of
On Wed, Mar 7, 2018 at 3:23 PM, Doug Gorley wrote:
> Good day,
>
> How does one monitor the status or progress of an initial sync under
> logical replication? For example:
>
> * I create a publication in database db_pub
> * I create a subscription in database db_sub
> * In 15 minutes I want to c
I'm wanting to change the ON UPDATE behavior of several foreign keys.
I know this has been "asked and answered" in the past, and I have a
query that will generate one-statement-per-fkey DDL, but while
tailoring that query I noticed that pg_constraint's confupdtype could
just be changed to 'c' direc
Hi,
I have a SQL script that does some DDLs, inserts and counts.
The command I ran is
psql dbname -c "\i crscript.sql" > output.txt
In output.txt, I got something like
INSERT 0 1
INSERT 0 1
CREATE TABLE
INSERT 0 2
count
---
9
(1 row)
Is there a way to output the SQLs and DDLs so that
On 15 March 2018 at 14:57, Tiffany Thang wrote:
> Is there a way to output the SQLs and DDLs so that I could easily identify
> what statements were executed?
>
>
-a, --echo-all echo all input from script
Geoff
On 03/15/2018 07:57 AM, Tiffany Thang wrote:
Hi,
I have a SQL script that does some DDLs, inserts and counts.
The command I ran is
psql dbname -c "\i crscript.sql" > output.txt
In output.txt, I got something like
INSERT 0 1
INSERT 0 1
CREATE TABLE
INSERT 0 2
count
---
9
(1 row)
Is
On Thu, Mar 15, 2018 at 12:32 AM, Michael Paquier
wrote:
> > I'm running version 9.1.9 so it should be working according to the
> > wiki.
>
> You should update and upgrade. 9.1 has fallen out of community support
>
I will recommend that to the database owner. Thanks
On Thu, Mar 15, 2018 at 12:44 AM, Tom Lane wrote:
>
> The query does fail on < 9.2, because on rows with no reltoastrelid
>
Thats, fine. I will live with that until upgrade.
> But hey, it's a wiki;
> if you feel more ambitious, edit away.
>
I tried but it said:
"The site you are trying to log
*Hi All,*
*We are facing below error in my postgres 9.2 production database. Please
help us how to resolve and why we are facing this issue and impact of the
issue. *
*ERROR: right sibling's left-link doesn't match: block 5 links to 8
instead of expected 2 in index "pg_toast_2619_index"*
*CO
Hello,
I am using `SELECT * FROM queue ... FOR UPDATE SKIP LOCKED` to implement
a queueing system.
Now I wonder if it is possible, given the id of one of the locked rows
in the queue table, to find out which connection/which transaction owns
the lock.
Any help is greatly appreciated.
Than
Check out here: https://wiki.postgresql.org/wiki/Lock_Monitoring
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On Thu, Mar 15, 2018 at 1:30 PM, Enrico Thierbach wrote:
> Now I wonder if it is possible, given the id of one of the locked rows in
> the queue table, to find out which connection/which transaction owns the
> lock
>
I'd start here:
https://www.postgresql.org/docs/10/static/view-pg-locks.html
Thanks Geoff and Adrian!
On Thu, Mar 15, 2018 at 11:03 AM, Adrian Klaver
wrote:
> On 03/15/2018 07:57 AM, Tiffany Thang wrote:
>
>> Hi,
>> I have a SQL script that does some DDLs, inserts and counts.
>>
>> The command I ran is
>> psql dbname -c "\i crscript.sql" > output.txt
>>
>> In output.txt,
Greetings,
* Enrico Thierbach (e...@open-lab.org) wrote:
> I am using `SELECT * FROM queue ... FOR UPDATE SKIP LOCKED` to implement a
> queueing system.
>
> Now I wonder if it is possible, given the id of one of the locked rows in
> the queue table, to find out which connection/which transaction
On Thu, Mar 15, 2018 at 4:48 PM, Stephen Frost wrote:
> Greetings,
>
> * Enrico Thierbach (e...@open-lab.org) wrote:
> > I am using `SELECT * FROM queue ... FOR UPDATE SKIP LOCKED` to implement
> a
> > queueing system.
> >
> > Now I wonder if it is possible, given the id of one of the locked rows
Hi Melvin, hi everyone else,
thank you for your support, and for your query example. And oh yes, I
forgot to mention the postgres version, which is 9.6; but if I find a
solution which works in Version 10 then I could probably update.
I guess with your query I can figure out which connection h
Greetnigs,
* Enrico Thierbach (e...@open-lab.org) wrote:
> I guess with your query I can figure out which connection holds a lock, but
> it seems I cannot correlate those locks to the rows which actually are
> locked, since `pg_locks` seems not to reference this in any way.
What I gave you would
Hello All:
A number of our team members and I use pg_dump to export schema in an Ubuntu
16.04 environment, I happen to have a postgress 9.6.4 server
that runs in a docker container, and in some cases I see the following select
statement and fully qualified table names in the
CREATE TABLE and ALT
On 03/15/2018 04:00 PM, Foolish Ewe wrote:
Hello All:
A number of our team members and I use pg_dump to export schema in an
Ubuntu 16.04 environment, I happen to have a postgress 9.6.4 server
that runs in a docker container, and in some cases I see the following
select statement and fully qual
>I guess with your query I can figure out which connection holds a lock,
but it seems I cannot correlate those locks to the rows which actually are
locked, since pg_locks seems not to reference this in any way.
*Enrico,*
*FWIW, I really don't understand your need to identify the actual rows t
Greetings,
Please respond to my PgBackrest questions,if any one tested.
On Wed, Mar 14, 2018 at 10:54 PM, chiru r wrote:
> Hi Stephen,
>
> Thank you very much for your quick reply.
>
>
> On Wed, Mar 14, 2018 at 6:17 PM, Stephen Frost wrote:
>
>> Greetings,
>>
>> * chiru r (chir...@gmail.com) w
Greetings Melvin,
* Melvin Davidson (melvin6...@gmail.com) wrote:
> >I guess with your query I can figure out which connection holds a lock,
> but it seems I cannot correlate those locks to the rows which actually are
> locked, since pg_locks seems not to reference this in any way.
>
> *FWIW, I r
Greetings,
* chiru r (chir...@gmail.com) wrote:
> Please respond to my PgBackrest questions,if any one tested.
Please don't spam the lists repeatedly like this. The responses to this
mailing list are provided by the community on a volunteer basis and
repeated emails are more likely to discourage
On Thu, Mar 15, 2018 at 10:14 PM, Stephen Frost wrote:
> Greetings Melvin,
>
> * Melvin Davidson (melvin6...@gmail.com) wrote:
> > >I guess with your query I can figure out which connection holds a lock,
> > but it seems I cannot correlate those locks to the rows which actually
> are
> > locked,
Greetings,
* chiru r (chir...@gmail.com) wrote:
> On Wed, Mar 14, 2018 at 6:17 PM, Stephen Frost wrote:
> > * chiru r (chir...@gmail.com) wrote:
> > > I am testing Pgbackrest and I have few questions.
> >
> > Great!
> >
> > > 1. I used postures user to perform backups and restores with Pgbackrest
Greetings Melvin,
* Melvin Davidson (melvin6...@gmail.com) wrote:
> On Thu, Mar 15, 2018 at 10:14 PM, Stephen Frost wrote:
> > Changes will continue to be made between major versions of PostgreSQL
> > when they're deemed necessary; I'd suggest those applications be
> > prepared to adjust on a per
Melvin Davidson writes:
> Yes, Stephen, I certainly understand making changes to system catalogs
> _when necessary_. That being said, the first change was the renaming of
> pid to procpid in pg_stat_activity. However, I contend that was more
> because someone felt that it was more to make the co
28 matches
Mail list logo
