Thomas Güttler writes:
> I have 2.3TBytes of files. File count is 17M
>
> Up to now we use rsync (via rsnapshot) to backup our data.
Isn't putting those files into your database going to make any sort of
maintanance on your database cumbersome? How big is your database
currently? Is it worth gro
Hi
A final followup from my side to this post for anyone who may find this
thread in archives in the future.
On the 15th of August Jacob Bunk Nielsen wrote:
> On the 1st of July 2014 Jacob Bunk Nielsen wrote:
>
>> We have a PostgreSQL 9.3.4 running in an LXC container on Debian
&g
"Arze, Cesar" writes:
> creating template1 database in /mnt/pg_data/base/1 ... FATAL: could
> not open file "pg_xlog/00010001" (log file 0, segment
> 1): No such file or directory
We've seen something slightly similar when running PostgreSQL in a Linux
container. See this thread
Hi
On the 1st of July 2014 Jacob Bunk Nielsen wrote:
> We have a PostgreSQL 9.3.4 running in an LXC container on Debian
> Wheezy on a Linux 3.10.43 kernel on a Dell R620 server. Data are
> stored on a XFS file system. We are seeing problems such as:
>
> unexpected data beyond EO
Rebecca Clarke writes:
> At present when a function is being edited we keep note of when and
> by who within comments in the function's code.
That sounds cumbersome.
> Is there, or can anyone recommend, any open source software that
> tracks function activity when it comes to edits (not executi
David Wall writes:
> A pg_dump backup -- with most of the data stored as large objects --
> takes about 5 hours.
>
> But restoring that dump takes about 2 hours. So it's taking 2.5 times
> longer to back it up than to restore it.
Does top(1) reveal any bottlenecks?
Is the backup constrained b
Hi
Jacob Bunk Nielsen writes:
> We have a PostgreSQL 9.3.4 running in an LXC container on Debian
> Wheezy on a Linux 3.10.43 kernel on a Dell R620 server. Data are
> stored on a XFS file system. We are seeing problems such as:
>
> unexpected data beyond EOF in block 2 of relation
Patrick Simcoe writes:
> Does anyone have a technique or recommendation for two-way encryption
> which somehow obfuscates the decrypt key so that it isn't easily
> retrievable from the database or the application source code? We've
> already considered (a) letting users hold the decrypt key and (
Hi
We have a PostgreSQL 9.3.4 running in an LXC container on Debian
Wheezy on a Linux 3.10.43 kernel on a Dell R620 server. Data are
stored on a XFS file system. We are seeing problems such as:
unexpected data beyond EOF in block 2 of relation base/805208133/1238511128
and
could not read block
Hi
We have a PostgreSQL 9.3.4 running in an LXC container on Debian
Wheezy on a Linux 3.10.43 kernel on a Dell R620 server. Data are
stored on a XFS file system. We are seeing problems such as:
unexpected data beyond EOF in block 2 of relation base/805208133/1238511128
and
could not read block
10 matches
Mail list logo
