http://outlet.vanlooken.com/qqwcl/yqlivfckw.rcxaekidbyraanhw
Mag Gam
7/21/2013 7:23:01 AM
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
... well, 11 actually.
We are down to 3 patches needing review, 2 waiting on author, and 6
waiting on commit. Whatever folks can do to close out this commitfest
is very welcome!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
On Wed, 2013-07-17 at 13:43 -0400, Alvaro Herrera wrote:
> Tom Lane escribió:
>
> > My feeling about this code is that the reason we print the infomask in
> > hex is so you can see exactly which bits are set if you care, and that
> > the rest of the line ought to be designed to interpret the bits
> (For that matter, am I not supposed to commit between 'fests? Or is it
> still an option for me to finish up with this after I get back even if
> we close the CF?)
The idea of the CommitFests is to give committers some *time off*
between them. If a committer wants to commit stuff when it's not
On 21.07.2013 08:41, Jeff Davis wrote:
(For that matter, am I not supposed to commit between 'fests? Or is it
still an option for me to finish up with this after I get back even if
we close the CF?)
It's totally OK to commit stuff between 'fests.
- Heikki
--
Sent via pgsql-hackers mailing li
On Fri, 2013-07-19 at 09:39 -0700, Josh Berkus wrote:
> So ... are you doing a final review of this for the CF, Jeff? We need
> to either commit it or bounce it to the next CF.
I am going on vacation tomorrow, and I just didn't quite find time to
take this to commit. Sorry about that, Nicholas. T
On Saturday, July 20, 2013 9:53 PM tubadzin wrote:
> Hi.
> 1.I downloaded source code PostgreSql version 9.2.4. from
> http://www.postgresql.org/ftp/source/
> 2.Next, I downloaded ActivePerl and installed it. Next, I used Visual Studio
> x64 Win64 command prompt 2010. Later I used visual studi
Hello all
I very often use a little bit adjusted psql system queries to
detection TOP N sized tables. I am thinking so it can be useful for
all users
I propose a few new commands
\dts [N|size] ... show N largest tables | show tables larger than size
ordered by size
\dis [N|size] ... show N large
On Thu, Jun 27, 2013 at 10:31 PM, Tom Lane wrote:
>
> AFAIR, no one has ever done a serious comparison to anything except GNU
> indent, and (at least at the time) it seemed to have bugs as bad as
> pgindent's, just different ones. I'm certainly open to another choice
> as long as we don't lose on
objectaccess.h has this to say:
* OAT_POST_ALTER should be invoked just after the object is altered,
* but before the command counter is incremented. An extension using the
* hook can use SnapshotNow and SnapshotSelf to get the old and new
* versions of the tuple.
That's a clever design, but
On 20.07.2013 19:28, Greg Smith wrote:
On 7/20/13 4:48 AM, didier wrote:
With your tests did you try to write the hot buffers first? ie buffers
with a high refcount, either by sorting them on refcount or at least
sweeping the buffer list in reverse?
I never tried that version. After a few roun
On 7/20/13 4:48 AM, didier wrote:
With your tests did you try to write the hot buffers first? ie buffers
with a high refcount, either by sorting them on refcount or at least
sweeping the buffer list in reverse?
I never tried that version. After a few rounds of seeing that all
changes I tried
Hi.
1.I downloaded source code PostgreSql version 9.2.4. fromÂ
http://www.postgresql.org/ftp/source/
2.Next, I downloaded ActivePerl and installed it. Next, I used Visual Studio
x64 Win64 command prompt 2010. Later I used visual studio command prompt for
get into path source code :
"C:\Postgresq
2013/7/19 Dean Rasheed :
> On 19 July 2013 04:09, Greg Smith wrote:
>> On 7/18/13 11:03 PM, Stephen Frost wrote:
>>>
>>> Wasn't there a wiki page about this
>>> feature which might also help? Bigger question- is it correct for the
>>> latest version of the patch?
>>
>>
>> https://wiki.postgresql.
2013/7/19 Stephen Frost :
> * Greg Smith (g...@2ndquadrant.com) wrote:
>> On 7/18/13 7:57 PM, Karol Trzcionka wrote:
>> >Current head 4cbe3ac3e86790d05c569de4585e5075a62a9b41 -> patch applies
>> >correct (only change needed in parallel_schedule).
>> >However it fails on own regression tests (other
Sent from my iPad
On 20-Jul-2013, at 15:26, mohsen soodkhah mohammadi
wrote:
> hello.
> dose one create index on the large table changes the place of some tuples in
> some pages?
No, making an index involves keeping some metadata about your tables in an
auxiliary data structure. It will r
On 20.07.2013 12:56, mohsen soodkhah mohammadi wrote:
hello.
dose one create index on the large table changes the place of some tuples
in some pages?
No, creating an index doesn't move any tuples in the heap.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To m
On Thu, 2013-07-18 at 21:34 -0400, Tom Lane wrote:
> Yeah, this is randomly different from everywhere else in PG. The more
> usual convention if you want typedefs for both the struct and the
> pointer type is that the pointer type is FooBar and the struct type is
> FooBarData.
I think that is mor
hello.
dose one create index on the large table changes the place of some tuples
in some pages?
Hi
With your tests did you try to write the hot buffers first? ie buffers with
a high refcount, either by sorting them on refcount or at least sweeping
the buffer list in reverse?
In my understanding there's an 'impedance mismatch' between what postgresql
wants and what the OS offers.
when it ca
20 matches
Mail list logo
