Am 30.04.2021 um 13:41 schrieb Laurenz Albe:
> Please reply to the list> Sorry my mistake, I fixed this.
> On Fri, 2021-04-30 at 13:20 +0200, Wolfgang Rißler wrote:
>> Thanks for answering, but
>> I didn't ask for a PostgreSQL client. I asked for the c-language-lib
>> libpq. (which is maybe used
Am 30.04.2021 um 13:00 schrieb Laurenz Albe:
On Fri, 2021-04-30 at 10:49 +0200, Wolfgang Rißler wrote:
we are (unfortunately) on windows with our DB and our application.
Now we want to switch to a new version of Postgres, because we want to
use logical replication (to replace our old Postgres
On Fri, Apr 30, 2021 at 7:12 AM Thomas Munro wrote:
> But do you have lots of short overlapping transactions so that there
> is never a moment where there are zero transactions running?
Yeah, that almost certainly explains it.
Thanks very much for the explanation about the summarized locks.
>
On Sat, Mar 13, 2021 at 08:43:54AM -0500, Jan Wieck wrote:
> On 3/12/21 8:30 PM, Michael Paquier wrote:
> > Hi Jan,
> >
> > On Fri, Mar 12, 2021 at 06:13:33PM -0500, Jan Wieck wrote:
> > > One of the things in my way is that when using pg_resetwal to put the
> > > NextXID way into the future (to
Maarten Mortier writes:
> We have a jsonb_ops GIN index on this field, because we query the following
> "freeform" match:
> SELECT COUNT(id)
> FROM records
> WHERE data @@ '$.**.label == "person"';
> However, in the case of jsonb queries above, there is no need to do the
> BitmapHeapScan
=?UTF-8?Q?Wolfgang_Ri=c3=9fler?= writes:
> The problem is, that our application (IDE MS-VisualStudio, C++) has to
> be 32bit, because of some old 32bit-dll's, which we cant kick out at the
> moment.
> So I compiled a libpqxx with the last 32bit libpq (which is v10).
Uh ... what's this about
On Wed, Apr 28, 2021 at 2:25 AM Mike Beachy wrote:
> On Tue, Apr 27, 2021 at 2:56 AM Laurenz Albe wrote:
>>
>> Not sure, but do you see prepared transactions in "pg_prepared_xacts"?
>
> No, the -1 in the virtualtransaction
> (https://www.postgresql.org/docs/11/view-pg-locks.html) for
Were there any issues with hardware ?
Memory/storage ?
I am not sure but it look like data loss to me.
If you have admin access?
Can you run dmesg -a, system logs, hyperion logs etc and see if there are
any errors related to memory corruption.
Coz if there are hardware issues, this will happen
On Fri, 2021-04-30 at 10:49 +0200, Wolfgang Rißler wrote:
> we are (unfortunately) on windows with our DB and our application.
> Now we want to switch to a new version of Postgres, because we want to
> use logical replication (to replace our old Postgres 8.3 with
> slony-replication).
>
> The
Hello community,
we are (unfortunately) on windows with our DB and our application.
Now we want to switch to a new version of Postgres, because we want to
use logical replication (to replace our old Postgres 8.3 with
slony-replication).
The problem is, that our application (IDE
Hello,
We have a table with raw jsonb data in a field "data".
We have a jsonb_ops GIN index on this field, because we query the following
"freeform" match:
SELECT COUNT(id)
FROM records
WHERE data @@ '$.**.label == "person"';
When analysing this plan, it seems the BitmapIndexScan to do this is
Il giorno gio 29 apr 2021 alle ore 19:13 Paul Förster <
paul.foers...@gmail.com> ha scritto:
> nothing of it was a FUD. It was a comparison done on a single machine.
> Then, I drew my conclusions from that and added my personal view. You don't
> necessarily havet to agree to my opinion nor did I
I am not sure which postgresql client is being referred to.
If it is psql command line then from the notes section of the docs below
says
https://www.postgresql.org/docs/current/app-psql.html
psql works best with servers of the same or an older major version.
Backslash commands are particularly
Hi Team,
Do we have any reference documentation which tells above postgres client's
backward compatibility ?
Example: I am having PG server installed is PG-11.8 and PG client installed
is PG-13 , will I face any issue? or are there any limitations if I use it ?
Regards,
Rajesh Madiwale.
14 matches
Mail list logo
