summaryrefslogtreecommitdiff
path: root/doc/faq.html
diff options
context:
space:
mode:
authoreinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2006-09-26 06:17:22 +0000
committereinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2006-09-26 06:17:22 +0000
commit8062addebc9c881e03344bbd4ae33745f36bee12 (patch)
tree2605df58158b7527323a2d3af25690f20d63ed16 /doc/faq.html
parent7cda38de04c3df65c02f54423abfd729649439db (diff)
Minor documentation changes
git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@155 4979c152-3d1c-0410-bac9-87ea11338e46
Diffstat (limited to 'doc/faq.html')
-rwxr-xr-xdoc/faq.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/faq.html b/doc/faq.html
index dc739e05..59831b9c 100755
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -37,10 +37,10 @@ Unfortunately, since this problem involves information loss, no
solution can be automated without invalidating your accounting
information. </li></p>
-<p><li><h4>PostgreSQL 8.x</h4>
+<p><li><h4>Restoring old SQL-Ledger backups</h4>
PostgreSQL added a restriction in v8.x that a sequence cannot be dropped
after if it is referenced by a table. However backups created with
-LedgerSMB v2.6.13 and earlier have a DROP SEQUENCE step in the backup
+SQL-Ledger v2.6.13 and earlier have a DROP SEQUENCE step in the backup
which will fail. To fix this edit the backup before restoring on a 8.x
system.