Amador Alvarez writes:
> Hi there,
> I would like to know if it is possible to get the date when the
> different schemas were created, as I want to write an script to dump
> only the latest schemas, the latest month created schemas for
> instance.
You could attach the creation date to the schema
Hi,
I have configured PG master and slave to run under synchronous replication mode
and they are mostly working fine. Except during the setup phase. Please read
thru my setup, procedure and let me know if I am doing something stupid.
PG master :
wal_level = hot_standby
max_wal_senders = 5
Hi,
On Wed, 6 Jun 2012 14:55:15 +, Manoj Govindassamy
wrote:
PG Slave gets fresh backup from PG master using pg_backup utility
everytime before it starts up
That's not necessary. Usually you do this only the first time you set
it up, then take advantage of the wal_keep_segments on the m
Hello, I am setting up a new postgres production server in a managed
hosting environment. I dont have much insight into the underlying disk
architecture but the filesystem I have been presented with has a 4k block
size. Postgres defaults to 8k block size; would it be beneficial to repave
the file
Gabriele,
Thanks for the quick reply.
> That's not necessary. Usually you do this only the first time you set
> it up, then take advantage of the wal_keep_segments on the master and
> allow the standby to resync.
we are not sure about when the standby will come again and sync with master.
also
Mike Broers writes:
> Hello, I am setting up a new postgres production server in a managed
> hosting environment. I dont have much insight into the underlying disk
> architecture but the filesystem I have been presented with has a 4k block
> size. Postgres defaults to 8k block size; would it be
"Igor Shmain" wrote:
> Would it be possible for you to mention what hardware (cpu, ram,
> disks, etc.) and software your system uses to support this db size
> and number of transactions?
We have 4 Intel Xeon X7350 @ 2.93GHz for 16 cores with 128GB RAM.
We've got a pair of drives in RAID 1 fo
What are the key benefits of using hstore over simple K:V storage in Postgres
where you split the key in its own column and value in its own column ?
Thank you for any inputs.
Thanks hary and Matthias,
It is a very good idea, however the schema names are meaningful and not
allowed to be attached to a date.
Regarding the comment solution ("COMMENT ON SCHEMA x IS 'y'"), it sounds
great and I tried to run different examples without happy ending as 'y'
must be a literal
You don't need to do an entity attribute value model in a separate table
to include mutliple key value pairs. since an hstore is schemaless, you
can include them all in one column for a particular row.
On 06/06/2012 04:33 PM, A J wrote:
What are the key benefits of using hstore over simple K:V
10 matches
Mail list logo
