Grokbase
x

Guillaume Lelarge (guil...@lelarge.info)

Profile | Posts (61)

User Information

Display Name:Guillaume Lelarge
Partial Email Address:guil...@lelarge.info
Posts:
61 total
6 in PostgreSQL - Admin
20 in PostgreSQL - Advocacy
24 in PostgreSQL - Docs
4 in PostgreSQL - General
2 in PostgreSQL - Performance
1 in PostgreSQL - PHP
4 in PostgreSQL - SQL

5 Most Recent

All Posts
1) Guillaume Lelarge [pgsql-advocacy] Re: [pgsql-eu-general] The Italian PostgreSQL Users Group is finally a non profit organisation
| +1 vote
Gabriele Bartolini a écrit : Congrats :) The french organization is a non-profit one entirely...
PostgreSQL - Advocacy
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Gabriele Bartolini a écrit :
> I am really proud to announce that last Saturday, 17 november 2007,
> the Italian PostgreSQL Users Group has been founded by twelve volunteers
> and that today the non-profit organisation has been officially registered.
>

Congrats :)

> As far as I know, this is the second non-profit organisation entirely
> dedicated to PostgreSQL ever to be founded in Europe - after the great
> French one (I might be wrong though, in that case please correct me).
>

The french organization is a non-profit one entirely dedicated to
PostgreSQL. It seems to me it was the first. Anyways, congrats. You've
done a terrific job (pgDay event, and now a non-profit organization...
nothing will stop you :) ).

> [...]
> This process has taken a few months and has been the natural produce
> of PGDay. Most of the founders indeed took part in the organisation of
> the biggest gathering of the PostgreSQL community ever to be held in
> Europe (so far). ;-)
>

+1

> Although IT-PUG is still in its startup phase, users can find some
> information (including the statute - in Italian) on the website:
> www.itpug.org . Hopefully soon IT-PUG will be ready to accept
> subscriptions online as well.
>

I would have some questions to ask. For example, the purpose of the
organization is to prepare "events, conferences, courses"... so this is
mainly advocacy stuff ? or do you also plan to contribute on
translations, coding, etc. ? On the translation side, I know that
Giuseppe Sacco is doing a really great work (100% done for 1.8). But I
don't see any translation of pginstaller (PostgreSQL Windows Installer),
and the PostgreSQL translation is at most at 60%. Do you think your
organization can work on some of these ? this is also kind of advocacy
work :) And what about the manual ? Last question, do you know italian
people coding on a PostgreSQL project ?

Whooo, that's really a lot of questions, sorry about that :) with your
answers, I'll probably write a small paper for postgresqlfr.org. Thanks :)


--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
match
2) Guillaume Lelarge [DOCS] Deux typo fixes...
| +1 vote
This is a multi-part message in MIME format. Content-Type: text/plain; charset=ISO-8859-1...
PostgreSQL - Docs
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
This is a multi-part message in MIME format.
--------------070106060906020201000106
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

... this time in textsearch.sgml. Please apply. Thanks.

Regards.


--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

--------------070106060906020201000106
Content-Type: text/x-patch;
name="textsearch.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="textsearch.patch"

Index: doc/src/sgml/textsearch.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/textsearch.sgml,v
retrieving revision 1.29
diff -r1.29 textsearch.sgml
2063c2063
<     The mising positions 1,2,4 are because of stop words.  Ranks
---
> The missing positions 1,2,4 are because of stop words. Ranks
2545c2545
<     at the end of the dictionary list. It it useless to have it
---
> at the end of the dictionary list. It is useless to have it

--------------070106060906020201000106
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

--------------070106060906020201000106--
3) Guillaume Lelarge Re: Optimizing PostgreSQL for Windows
| +1 vote
Christian Rengstl a écrit : 32MB for shared_buffers seems really low to me but 2500MB for work_mem...
PostgreSQL - Performance
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Christian Rengstl a écrit :
> My OS is Windows 2003 with 4GB Ram and Xeon Duo with 3.2 GHz;
> shared_buffers is set to 32MB (as I read it should be fairly low on
> Windows) and work_mem is set to 2500MB, but nevertheless the query takes
> about 38 seconds to finish. The table "table1" contains approx. 3
> million tuples and table2 approx. 500.000 tuples. If anyone could give
> an advice on either how to optimize the settings in postgresql.conf or
> anything else to make this query run faster, I really would appreciate.
>

32MB for shared_buffers seems really low to me but 2500MB for work_mem
seems awfully high. The highest I've seen for work_mem was something
like 128MB. I think the first thing you have to do is to really lower
work_mem. Something like 64MB seems a better bet at first.

Regards.
4) Guillaume Lelarge [DOCS] Two fixes for 8.3b1 references
| +1 vote
Hi, You'll find attached a patch that fixes two mistakes in 8.3b1 manual. Please apply. Thanks....
PostgreSQL - Docs
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Hi,

You'll find attached a patch that fixes two mistakes in 8.3b1 manual.
Please apply. Thanks.

Regards.


--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com Index: doc/src/sgml/ref/create_type.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v
retrieving revision 1.72
diff -r1.72 create_type.sgml
615c615
<     serial id,
---
>     id serial,
Index: doc/src/sgml/ref/psql-ref.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v
retrieving revision 1.195
diff -r1.195 psql-ref.sgml
1660c1660
<           which will enable or display the tuples only mode.  If the
---
> which will enable or disable the tuples only mode. If the ---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

X-JEM-Mbox-From: From pgsql-docs-owner+m4528=archive=grokbase.com@postgresql.org Sat Oct 27 16:01:12 2007
X-JEM-Version: 1.1
5) Guillaume Lelarge Re: [DOCS] Tips needed for contrib doc
| +1 vote
Hi, Albert Cervera i Areny a écrit : I think this is the better way to do it. Even if it means to...
PostgreSQL - Docs
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Hi,

Albert Cervera i Areny a écrit :
> I wanted to spend a week or so putting the contrib doc into shape so I want
> to start by moving the contrib part from a new appendix to the Reference
> part.
>  The problems I find are:
> - I can't make this "contrib" doc a part because Reference already is a part
> and can't be nested.
>  Structure:
>  <part id="reference">
>   <part id="contrib">
>   
> - If I make the contrib doc a chapter in the index shows with an arabic
> number not as a roman one.
>  Structure:
>  <part id="reference">
>   <chapter id="contrib">
>
> - I can't make the doc a <reference> because first I need to point to the
> modules and not all of them are documented like a reference.
>  Structure:
>  <part id="reference">
>   <reference id="contrib">
>

I think this is the better way to do it. Even if it means to rewrite the
README to look like a reference.

> - If I leave it as it is now [1] the problem is that very small chapters just
> don't look right IMHO. Take a look at [2], for example. It should be a module
> per page in most cases except very long ones.
>  Structure:
>  <part id="contrib">
>   <chapter id="adminpack">
>
> Does anyone have a solution on this? I'm no docbook expert, so I might be very
> wrong.
>

The only (or simplest) way to have one page per module is to use the
reference part.

Regards.


--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

spacer
Profile | Posts (61)
Home > People > Guillaume Lelarge