[Pgpool-hackers] First try at rephrasing the documentation

[Tatsuo Ishii]

>> TODO: What is the point of 'flushing the sequences' ? Don't we trust
>> WAL recovery ?
>> A: PostgreSQL does not log sequence value whenever it counts
>> up. Instead it logs 'discretely'. So just redoing from WAL, it's
>> possible that slave loses upto 32 sequences. See
>> src/backend/commands/sequence.c.
> I still don't get it. The purpose of this is just to avoid having a hole of 32 
> values in the sequence ? 

No, it's not to avoid the hole.

> Or is it useful in replication mode and not in 
> master-slave?

Yes, it's only usefull in replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

Because having a hole in a sequence is something that happens 
> all the time.
> 
>> 
>> TODO: contradiction in the previous sentence md5 is supported by using
>> "pool_passwd".
>> A: You are correct.
> Yes, but is clear text password supported or not ? :)
> 
>> 
>> TODO: what happens then ? Is it rejected ?
>> A: No. Inconsistent values will be inserted.
> Ok, corrected
> 
>> 
>> TODO: I don't really get this one. Can somebody explain ?
>> A: Me neither:-) Let me check...
>> 
>> <p>The USING CLAUSE is converted to an ON CLAUSE by the query rewrite
>> process. Therefore, when "*" is used at target list, the row of the same
>> column name appears.</p> TODO: What does it mean ?
>> A: I don't know neither:-) Let me check...
>> 
>> TODO: This following section may be completely false. I tried to
>> understand the general meaning of the original text, and look into
>> pgpool's code to understand.
>> A: Let me check...
> Ok, I'll wait on these 3 ones too.
> 
> Marc Cousin
> Dalibo