Heikki Linnakangas wrote:
> Bruce Momjian wrote:
> > Pavan Deolasee wrote:
> >> On Fri, Feb 26, 2010 at 8:19 AM, Bruce Momjian wrote:
> >>
> >>> Whatever happened to this? It was in the first 9.0 commitfest but was
> >>> returned with feedback but never updated:
> >>>
> >>>
> >> Though Alex did s
Bruce Momjian wrote:
> Pavan Deolasee wrote:
>> On Fri, Feb 26, 2010 at 8:19 AM, Bruce Momjian wrote:
>>
>>> Whatever happened to this? It was in the first 9.0 commitfest but was
>>> returned with feedback but never updated:
>>>
>>>
>> Though Alex did some useful tests and review, and in fact con
Pavan Deolasee wrote:
> On Fri, Feb 26, 2010 at 8:19 AM, Bruce Momjian wrote:
>
> >
> > Whatever happened to this? It was in the first 9.0 commitfest but was
> > returned with feedback but never updated:
> >
> >
> Though Alex did some useful tests and review, and in fact confirmed that the
> VAC
On Fri, Feb 26, 2010 at 8:19 AM, Bruce Momjian wrote:
>
> Whatever happened to this? It was in the first 9.0 commitfest but was
> returned with feedback but never updated:
>
>
Though Alex did some useful tests and review, and in fact confirmed that the
VACUUM time dropped from 16494 msec to 366
On Thu, Feb 25, 2010 at 10:32 PM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Thu, Feb 25, 2010 at 9:49 PM, Bruce Momjian wrote:
>> > Whatever happened to this? ?It was in the first 9.0 commitfest but was
>> > returned with feedback but never updated:
>> >
>> > ? ? ? ?https://commitfest.postg
Robert Haas wrote:
> On Thu, Feb 25, 2010 at 9:49 PM, Bruce Momjian wrote:
> > Whatever happened to this? ?It was in the first 9.0 commitfest but was
> > returned with feedback but never updated:
> >
> > ? ? ? ?https://commitfest.postgresql.org/action/patch_view?id=75
>
> Well, the patch author c
On Thu, Feb 25, 2010 at 9:49 PM, Bruce Momjian wrote:
> Whatever happened to this? It was in the first 9.0 commitfest but was
> returned with feedback but never updated:
>
> https://commitfest.postgresql.org/action/patch_view?id=75
Well, the patch author chose not to pursue it. It's clea
Whatever happened to this? It was in the first 9.0 commitfest but was
returned with feedback but never updated:
https://commitfest.postgresql.org/action/patch_view?id=75
---
Pavan Deolasee wrote:
> ISTM that the PD
On Tue, Jul 21, 2009 at 2:37 AM, Pavan Deolasee wrote:
> On Tue, Jul 21, 2009 at 10:38 AM, Robert Haas wrote:
>> Pavan, are you planning to respond to Alex's comments and/or update this
>> patch?
>
> Yes, I will. Hopefully by end of this week.
Since it has now been 10 days since this patch was r
On Tue, Jul 21, 2009 at 10:38 AM, Robert Haas wrote:
>
> Pavan, are you planning to respond to Alex's comments and/or update this
> patch?
>
Yes, I will. Hopefully by end of this week.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers ma
On Wed, Jul 15, 2009 at 11:44 PM, Alex Hunsaker wrote:
> On Mon, Dec 8, 2008 at 06:56, Pavan Deolasee wrote:
>> Here is a patch which implements this. The PD_ALL_VISIBLE flag is set if all
>> tuples in the page are visible to all transactions and there are no DEAD
>> line pointers in the page. The
On Mon, Dec 8, 2008 at 06:56, Pavan Deolasee wrote:
> Here is a patch which implements this. The PD_ALL_VISIBLE flag is set if all
> tuples in the page are visible to all transactions and there are no DEAD
> line pointers in the page. The second check is required so that VACUUM takes
> up the page.
Bruce Momjian wrote:
Pavan Deolasee wrote:
On Mon, Dec 8, 2008 at 11:33 AM, Pavan Deolasee wrote:
On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
If you see a straightforward way, please submit a patch!
Will do that.
Here is a patch whi
Pavan Deolasee wrote:
> On Mon, Dec 8, 2008 at 11:33 AM, Pavan Deolasee
> wrote:
>
> >
> >
> > On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
> > heikki.linnakan...@enterprisedb.com> wrote:
> >
> >>
> >> If you see a straightforward way, please submit a patch!
> >>
> >>
> > Will do that.
>
> Yeah, I dropped the ball on that one. It's been knocking in the back of my
> head since, but I've never gotten around. I'm feeling reluctant to review it
> since it's not really a high priority thing, and I'm not sure whether we
> want it or not.
In that case perhaps we should add it to
http://w
Pavan Deolasee wrote:
On Thu, Jan 15, 2009 at 7:10 AM, Bruce Momjian wrote:
Is this something for 8.4 CVS?
I worked out the patch as per Heikki's suggestion. So I think he needs
to review and decide it's fate.
Yeah, I dropped the ball on that one. It's been knocking in the back of
my head
On Thu, Jan 15, 2009 at 7:10 AM, Bruce Momjian wrote:
>
> Is this something for 8.4 CVS?
>
I worked out the patch as per Heikki's suggestion. So I think he needs
to review and decide it's fate.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hac
Is this something for 8.4 CVS?
---
Pavan Deolasee wrote:
> On Mon, Dec 8, 2008 at 11:33 AM, Pavan Deolasee
> wrote:
>
> >
> >
> > On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
> > heikki.linnakan...@enterprisedb.com
On Mon, Dec 8, 2008 at 11:33 AM, Pavan Deolasee <[EMAIL PROTECTED]>wrote:
>
>
> On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
> [EMAIL PROTECTED]> wrote:
>
>>
>> If you see a straightforward way, please submit a patch!
>>
>>
> Will do that.
>
>
Here is a patch which implements this. The PD
On Sat, Dec 6, 2008 at 8:08 PM, Heikki Linnakangas <
[EMAIL PROTECTED]> wrote:
>
> If you see a straightforward way, please submit a patch!
>
>
Will do that.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
Pavan Deolasee wrote:
ISTM that the PD_ALL_VISIBLE flag and the visibility map bit can be set at
the end of pruning operation if we know that there are only tuples visible
to all transactions left in the page.
Right.
The way pruning is done, I think it
would be straight forward to get this in
ISTM that the PD_ALL_VISIBLE flag and the visibility map bit can be set at
the end of pruning operation if we know that there are only tuples visible
to all transactions left in the page. The way pruning is done, I think it
would be straight forward to get this information.
Thanks,
Pavan
--
Pava
22 matches
Mail list logo