On Wed, Jan 17, 2018 at 12:16:19PM -0500, Tom Lane wrote:
> The basic thrust of these messages is "I'm reading what should be
> sequentially numbered data chunks for this toast OID, and the sequence
> numbers are wrong". Both of these instances could be explained by
> duplicate toast rows (or dupl
Hi Tom,
On Wed, Jan 17, 2018 at 7:56 PM, Tom Lane wrote:
> =?UTF-8?Q?Jacek_Ko=C5=82odziej?= writes:
> > Here's what happening to me: the "A" query occasionally (in my case: on
> the
> > order of tenths per day) returns an ID _higher_ than any ID present in
> > second query's result (other condi
Hi,
I'm creating an application( microservice architecture using dokcer
containers) and I need to save a huge number of data in multiple tables in
the same time.
I have a table provider which has the different columns: name, status,
address, contact.
The table establishment contains: name, status,
Please remove me from this list. Thanks.
Karen Stone| Technical Services| Eldorado |a Division of MphasiS
5353 North 16th Street, Suite 400, Phoenix, Arizona 85016-3228
Tel (928) 892 5735 | www.eldoinc.com | www.mphasis.com |kst...@eldocomp.com
-Original Message-
From: Tom Lane [mail
=?UTF-8?Q?Jacek_Ko=C5=82odziej?= writes:
> Here's what happening to me: the "A" query occasionally (in my case: on the
> order of tenths per day) returns an ID _higher_ than any ID present in
> second query's result (other conditions I haven't specified do _not_ filter
> any more rows than "id <=
Version 10.1, Community version from PGDG repo
OS RHEL 7.3
I may have discovered a situation in 10.1 where EXECUTEing a PREPARED
statement acting on JSON data in partitioned tables hangs in an
infinite loop for a particular set of data. Unfortunately, the data is
proprietary
Alvaro Herrera writes:
> Tom Lane wrote:
>> However, assuming you've gotten that detail right, then any file
>> you can't match up with a relfilenode value must be an orphan you
>> can just "rm".
> Maybe look in pg_buffercache for entries referencing those files before
> deleting. It would be su
Tom Lane wrote:
> However, assuming you've gotten that detail right, then any file
> you can't match up with a relfilenode value must be an orphan you
> can just "rm".
Maybe look in pg_buffercache for entries referencing those files before
deleting. It would be surprising to see any if no catalo
a...@novozymes.com (Adam =?utf-8?Q?Sj=C3=B8gren?=) writes:
> Also, the error we are getting is now: "unexpected chunk number 2
> (expected 3) for toast value 1498303849 in pg_toast_10919630", where
> previously we've only seen "unexpected chunk number 0 (expected 1)".
> We are kind of at a loss, s
On Wed, Jan 17, 2018 at 10:45 AM, Jacek Kołodziej
wrote:
>
>
> 17.01.2018 3:30 PM "Melvin Davidson" napisał(a):
>
>
>
> On Wed, Jan 17, 2018 at 8:08 AM, Jacek Kołodziej
> wrote:
>
>> Hello everyone,
>>
>> this is my first post here and I'm starting with asking a question about
>> data consisten
Troy,
I am trying to get a windows instance up and running with pgaudit. my
question to you is how did you create the dll for pgaudit? I just cant seem
to create the extension.
Thanks
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
17.01.2018 3:30 PM "Melvin Davidson" napisał(a):
On Wed, Jan 17, 2018 at 8:08 AM, Jacek Kołodziej
wrote:
> Hello everyone,
>
> this is my first post here and I'm starting with asking a question about
> data consistency between two consecutive SELECTs using PostgreSQL 9.6.
>
> I'm sorry if tha
On Wed, Jan 17, 2018 at 3:30 PM, Melvin Davidson wrote:
> Just a suggestion. The first query is not really needed.
> You can simply do:
> second query (B):
>
> SELECT id
> , ...
> FROM events
> WHERE id > MIN(ID)
>AND id <= MAX(ID)
>AND ...
>
> See https://www.postgresql.org/docs/9
Melvin Davidson wrote:
> You can simply do:
> second query (B):
>
> SELECT id
> , ...
> FROM events
> WHERE id > MIN(ID)
>AND id <= MAX(ID)
>AND ...
You probably meant to use a window function there:
max(id) OVER ()
min(id) OVER ()
Yours,
Laurenz Albe
On Wed, Jan 17, 2018 at 8:08 AM, Jacek Kołodziej
wrote:
> Hello everyone,
>
> this is my first post here and I'm starting with asking a question about
> data consistency between two consecutive SELECTs using PostgreSQL 9.6.
>
> I'm sorry if that's something that was already discussed - I couldn't
Hello everyone,
this is my first post here and I'm starting with asking a question about
data consistency between two consecutive SELECTs using PostgreSQL 9.6.
I'm sorry if that's something that was already discussed - I couldn't find
it either in archives, nor in _general internet_. If it is, I
> And what is the difference between index scan and index only scan.
Index scan: Index lookup for key access plus read from data blocks to satisfy
the query.
Index only scan: Index lookup for key access plus read from index pages itself
to satisfy query. In other words, entire query can
be
17 matches
Mail list logo
