--On 30. Mai 2013 18:15:04 +0530 itishree sukla itishree.su...@gmail.com
wrote:
Thanks for the quick response. Below is the out put of Top Commnd.
3971 postgres 20 0 8048m 303m 301m S 0 0.9 0:04.34
/usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c
--On Samstag, September 08, 2007 12:39:37 -0400 Tom Lane
[EMAIL PROTECTED] wrote:
However, it seems like the point here is not so much can you recover
your data as what a commit means. Do you want a commit reported to the
client to mean the data is safely down to disk in both places, or only
--On Freitag, September 07, 2007 20:00:16 +0100 Simon Riggs
[EMAIL PROTECTED] wrote:
On Fri, 2007-09-07 at 11:37 +0200, Maila Fatticcioni wrote:
protocol C;
Try protocol B instead.
But that would have an impact on transaction safety, wouldn't it? It will
return immediately after
On Wed, 10 Jan 2007 15:30:16 -0600, Scott Marlowe [EMAIL PROTECTED] wrote:
[...]
And I don't think the mysql partition supports tablespaces either.
MySQL supports distributing partitions over multiple disks via the SUBPARTITION
clause [1].
I leave it to you, wether their syntax is
On Thu, 11 Jan 2007 08:18:39 -0600, Adam Rich [EMAIL PROTECTED] wrote:
Subpartitions are just a way to break (parent) partitions up into
smaller pieces. Those of course can be moved to other disks
just like the main partitions.
Ah, didn't know that (i just wondered why i need a
