On Thu, Apr 1, 2010 at 2:10 PM, Jonathan Foy wrote:
> Hello
>
> I came in this morning and noticed this warning sitting in my inbox quite a
> few times...
>
> WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation "table_2010q1"
> page 471118
> WARNING: PD_ALL_VISIBLE flag was incorrectly
oic, thanks ^^
--
Regards,
Kiswono P
GB
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Kiswono Prayogo escribió:
> Just reporting that Alpha 4 was working just fine..
> http://pastebin.com/ri2gXJDN
>
> but Alpha 5 didn't:
Yeah, known packaging bug. Please remove src/Makefile.custom and try
again (notice the -Werror that shouldn't be there)
> elog.c:1698: error: ignoring return v
Kiswono Prayogo writes:
> Just reporting that Alpha 4 was working just fine..
> http://pastebin.com/ri2gXJDN
> but Alpha 5 didn't:
If you got a copy that includes src/Makefile.custom, remove that and
try again.
regards, tom lane
--
Sent via pgsql-admin mailing list (pg
Just reporting that Alpha 4 was working just fine..
http://pastebin.com/ri2gXJDN
but Alpha 5 didn't:
make[4]: Entering directory
`/home/kyz/Repository/postgres/pgsql/src/backend/utils/error'
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -fno-stric
On Tue, Apr 6, 2010 at 3:45 AM, Timothy Madden wrote:
> The machine is a mini-laptop running almost all day time (actually
> there are many of them) and if the machine is captured it is likely to
> be captured while running.
Wait, stop right there. So, you're a thief and you just made off with
a
terminato...@gmail.com (Timothy Madden) writes:
> Andreas 'ads' Scherbaum wrote:
>
>> If someone captures the machine the bad guy can install a network
>> sniffer and steal the database passwords upon connect.
>
> I think protecting against a keylogger is a different issue than
> database encrypti
Renato Oliveira wrote:
What is the difference between:
archive_command = on (is this command for 8.2?)
|archive_mode = on (This one is for 8.3!)|
8.2 doesn't have a archive_mode setting, that was added in 8.3. With
8.2, you set the archive_command in the same way as you do in 8.3. There
j
Ok people thank you for your answers.
Timothy Madden
On Wed, Apr 7, 2010 at 3:25 PM, Michael Gould
wrote:
> Timothy,
>
> I've worked with SQL Anywhere which does have database encryption. There
> are pluses to having a encrypted db, but it did slow down the processing.
> They also had the abi
Suresh,
The real question is: does manipulation of the images have to be
transactional? If so, store them in the database. If not, store the images in
the file system and put the file name in the database, thereby avoiding
unecessary WAL overhead.
Bob Lunney
--- On Wed, 4/7/10, Suresh Borse
Suresh Borse wrote:
> How does PostGreSQL perform in case we have to store and use huge
> no of images:
>
> Eg 4000 * 1 images, each approx 2 MB size.
We have a database with a table containing 7.5 million rows, each
having an image in a bytea column. While the average size is only
15.2
Dear all,
I have been playing with PITR on version 8.3 so far, but I need to get it
working on version 8.2.
What is the difference between:
archive_command = on (is this command for 8.2?)
archive_mode =on (This one is for 8.3!)
I need to enable 'archive_mode = on', restart postgres, befo
How does PostGreSQL perform in case we have to store and use huge no of
images:
Eg 4000 – 1 images, each approx 2 MB size.
The Questions that we have are:
How do we handle such huge no of images so that the application does not
slow down?
How does PostGreSQL use caching? In case of im
Timothy,
I've worked with SQL Anywhere which does have database encryption. There
are pluses to having a encrypted db, but it did slow down the processing.
They also had the ability to encrypt stored procedures and triggers. That
didn't' seem to really slow down the system.
That being said, th
Timothy Madden wrote:
> [...]
> User authentication should be unrelated to encrypting the database
> owned by that user. You can think of it as if only the owner can ever
> connect to such a database, and his/her password is the encryption
> key, or as if any user that wishes to connect should pr
On Wed, Apr 7, 2010 at 1:07 AM, Kevin Grittner
wrote:
> Timothy Madden wrote:
>
[...]
> But the server needs to read certain data from the database
> directory in order to start. In particular, WAL files need to be
> read to get a clean start, and those can contain any data from the
> database t
Andreas 'ads' Scherbaum wrote:
> If someone captures the machine the bad guy can install a network
> sniffer and steal the database passwords upon connect.
I think protecting against a keylogger is a different issue than
database encryption. Is this why database encryption is "not needed"
for Po
17 matches
Mail list logo
