On Wed, Jun 03, 2015 at 04:53:46PM -0400, Robert Haas wrote:
> So here's a patch taking a different approach. In this approach, if
> the multixact whose members we want to look up doesn't exist, we don't
> use a later one (that might or might not be valid). Instead, we
> attempt to cope with the
(Sorry Jan for receiving this twice)
@ Roxanne & Jan:
Thank you both for your Input. I absolutely see your point against EAV.
I will work out two variants based on the specific solution, where i would
create a (bigger) Table for each group of similar products, and based on
the dynamic JSON soluti
On June 3, 2015 02:04:28 PM Roxanne Reid-Bennett wrote:
> I think you should evaluate your unease with having to update the database
> on release (potentially many times) carefully for what it is and why you
> have it. [I'm not saying it is invalid - just know why you have it]
> Because no matter
On Mon, Jun 1, 2015 at 4:55 PM, Noah Misch wrote:
> While testing this (with inconsistent-multixact-fix-master.patch applied,
> FWIW), I noticed a nearby bug with a similar symptom. TruncateMultiXact()
> omits the nextMXact==oldestMXact special case found in each other
> find_multixact_start() ca
Robert Haas wrote:
> So here's a patch taking a different approach.
I tried to apply this to 9.3 but it's messy because of pgindent. Anyone
would have a problem with me backpatching a pgindent run of multixact.c?
Also, you have a new function SlruPageExists, but we already have
SimpleLruDoesPhy
On Wed, Jun 3, 2015 at 8:24 AM, Robert Haas wrote:
> On Tue, Jun 2, 2015 at 5:22 PM, Andres Freund wrote:
>>> > Hm. If GetOldestMultiXactOnDisk() gets the starting point by scanning
>>> > the disk it'll always get one at a segment boundary, right? I'm not sure
>>> > that's actually ok; because th
Andres Freund wrote:
> On 2015-06-03 15:01:46 -0300, Alvaro Herrera wrote:
> > One idea I had was: what if the oldestMulti pointed to another multi
> > earlier in the same 0046 file, so that it is read-as-zeroes (and the
> > file is created), and then a subsequent multixact truncate tries to read
On 2015-06-03 15:01:46 -0300, Alvaro Herrera wrote:
> Andres Freund wrote:
> > That's not necessarily the case though, given how the code currently
> > works. In a bunch of places the SLRUs are accessed *before* having been
> > made consistent by WAL replay. Especially if several checkpoints/vacuum
Alvaro Herrera wrote:
> Really, the whole question of how this code goes past the open() failure
> in SlruPhysicalReadPage baffles me. I don't see any possible way for
> the file to be created ...
Hmm, the checkpointer can call TruncateMultiXact when in recovery, on
restartpoints. I wonder if in
On 6/3/2015 2:50 AM, Adrian Stern wrote:
Hi William, thanks for joining the conversation.
1) We do hope for constraints since a connection to an ERP system is
possible in the future. We want to plan ahead.
2) As for the subclass approach: I would need about 30 subclasses and
it will get real
Andres Freund wrote:
> On 2015-06-03 00:42:55 -0300, Alvaro Herrera wrote:
> > Thomas Munro wrote:
> > > On Tue, Jun 2, 2015 at 9:30 AM, Alvaro Herrera
> > > wrote:
> > > > My guess is that the file existed, and perhaps had one or more pages,
> > > > but the wanted page doesn't exist, so we tried
On 2015-06-03 00:42:55 -0300, Alvaro Herrera wrote:
> Thomas Munro wrote:
> > On Tue, Jun 2, 2015 at 9:30 AM, Alvaro Herrera
> > wrote:
> > > My guess is that the file existed, and perhaps had one or more pages,
> > > but the wanted page doesn't exist, so we tried to read but got 0 bytes
> > > ba
Thomas Munro wrote:
> I have finally reproduced that error! See attached repro shell script.
>
> The conditions are:
>
> 1. next multixact == oldest multixact (no active multixacts, pointing
> past the end)
> 2. next multixact would be the first item on a new page (multixact % 2048 ==
> 0)
>
Am 2015-06-03 19:00, schrieb Daniel Begin:
Sorry, my question might not have been clear…
I set myself the temp_tablespace to that location but did not expect
the drive could get full;
Multiple factors may have caused the drive to turn off (not
necessarily postgresql);
So, if that temp_tablespa
Sorry, my question might not have been clear…
I set myself the temp_tablespace to that location but did not expect the drive
could get full;
Multiple factors may have caused the drive to turn off (not necessarily
postgresql);
So, if that temp_tablespace gets full, how postgresql will react
Sent from my iPad
> On Jun 3, 2015, at 7:50 AM, Adrian Stern wrote:
>
> Hi William, thanks for joining the conversation.
>
> 1) We do hope for constraints since a connection to an ERP system is possible
> in the future. We want to plan ahead.
>
> 2) As for the subclass approach: I would ne
On Wed, Jun 3, 2015 at 11:14 AM, Daniel Begin wrote:
>
> A query
>
OK...
But ma question is: What append the temp_tablespace drive get full?
>
The query, probably...
"There is also a temp_tablespaces parameter, which determines the placement
of temporary tables and indexes, as well as temp
Context.
A query almost filled a SSD drive (temp_tablespace) and my PC got
unresponsive;
I did SELECT pg_cancel_backend(6600); 6600 was the pid of the process and
got a successful answer (t)
However, just after that, the disk simply turned off and the system crashed.
I was able to restart the P
On Tue, Jun 2, 2015 at 5:22 PM, Andres Freund wrote:
>> > Hm. If GetOldestMultiXactOnDisk() gets the starting point by scanning
>> > the disk it'll always get one at a segment boundary, right? I'm not sure
>> > that's actually ok; because the value at the beginning of the segment
>> > can very wel
On Wed, Jun 3, 2015 at 4:48 AM, Thomas Munro
wrote:
> On Wed, Jun 3, 2015 at 3:42 PM, Alvaro Herrera
> wrote:
>> Thomas Munro wrote:
>>> On Tue, Jun 2, 2015 at 9:30 AM, Alvaro Herrera
>>> wrote:
>>> > My guess is that the file existed, and perhaps had one or more pages,
>>> > but the wanted pa
Thank Bill,
About disks performance, all drives are identical and connected using USB3
connections and yes, I can tweak values and restart Postgres without any
hardship!-)
About seq_page_cost and random_page_cost, I am about to test different lower
values as you and Thomas propose.
Raising the sta
On Wed, Jun 3, 2015 at 3:42 PM, Alvaro Herrera wrote:
> Thomas Munro wrote:
>> On Tue, Jun 2, 2015 at 9:30 AM, Alvaro Herrera
>> wrote:
>> > My guess is that the file existed, and perhaps had one or more pages,
>> > but the wanted page doesn't exist, so we tried to read but got 0 bytes
>> > back
22 matches
Mail list logo
