Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.databases.postgresql Subject: Re: Issues with backing up Postgres by copying folder Date: Thu, 11 May 2017 23:08:11 +0200 Lines: 28 Message-ID: References: <20170419201146.02a1844344207bc63a19edcf@shallow.house> <20170502000731.7d5f6e4492d851c4800bd500@shallow.house> <20170503135752.28849ad7e804bc191bab0104@shallow.house> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net mI8lBeXBqvy0JN2kOAQ+hAyBpJdZaQnUp+liZL2WjBf5VfEf4= Cancel-Lock: sha1:3i6CT+WoNudFy9zTZVokgUwFTec= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 In-Reply-To: Xref: csiph.com comp.databases.postgresql:766 On 11.05.2017 17:11, DFS wrote: > On 5/3/2017 8:57 AM, Terry Shanks wrote: >> There is a body of evidence to suggest SQLite is faster than many >> multiuser rdbms' for general use but apparently CREATE INDEX is one >> thing it does fall behind in. > > Apparently it creates an empty table with the new structure, copies the > data from the old table, then deletes the old table. I do not understand: what do you mean by "new structure"? When creating an index there is no new structure. Or are you somehow alluding to changing the primary key of a table? https://sqlite.org/withoutrowid.html > Extremely inefficient. That would be the case. I doubt though that SQLite does it for every index creation. Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/