[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fossil-users
Subject:    [fossil-users] Shouldn't .DUMP preserve the page size?
From:       "Tony Papadimitriou" <tonyp () acm ! org>
Date:       2017-04-09 21:45:32
Message-ID: 0854A38FEBAD48069DF3B0CFDD8147CC () Yulichka
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Although not a critical issue, I think a dump should preserve the original database's \
page size (pragma page_size). Some databases have been squeezed significantly by \
using some non-default value. I feel this optimization should not be lost when \
restoring from a dump.

(I suppose there may be other pragma settings related that could/should be preserved \
by a .dump but I'm not sure at this point.)


[Attachment #5 (text/html)]

<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Comic Sans MS'; COLOR: #000000">
<DIV>Although not a critical issue, I think a dump should preserve the original 
database's page size (pragma page_size).</DIV>
<DIV>Some databases have been squeezed significantly by using some non-default 
value.</DIV>
<DIV>I feel this optimization should not be lost when restoring from a 
dump.</DIV>
<DIV>&nbsp;</DIV>
<DIV>(I suppose there may be other pragma settings related that could/should be 
preserved by a .dump but I'm not sure at this point.)</DIV>
<DIV>&nbsp;</DIV></DIV></DIV></BODY></HTML>

[Attachment #6 (text/plain)]

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic