Hi,
Is it easily possible to supply and receive tsrange types in epoch values, or
is it really all down always to string parsing?
As a general rule, I pass time in the app in epoch-float values, which is then
converted by the presenter/controller layer to the right format used by views,
wheth
On 17 Mar 2013, at 04:30, Tom Lane wrote:
> Oleg Alexeev writes:
>> * it is varchar columns, 256 and 32 symbols length
>> * encoding, collation and ctype: UTF8, en_US.utf8, en_US.utf8
>> * autovacuum, fsync off, full_page_writes = on, wal_writer_delay = 500ms,
>> commit_delay = 100, commit_sibl
On 13 Mar 2013, at 13:26, Shaun Thomas wrote:
> On 03/12/2013 05:49 PM, Gregg Jaskiewicz wrote:
>
>> So out of 6 disks then having 4 in Raid 1+0 configuration and other
>> two in mirror for WAL. That's another option then for me to test.
>
> That is an option, but it's not necessarily a good
On 4 Mar 2013, at 13:21, Vincent Veyron wrote:
>
> There is this :
>
> http://wiki.postgresql.org/wiki/Postgres-XC
>
>
> [Disclaimer : I can't tell whether it's usable or not; I just know they
> exist]
>
Well, I know of its existence too. Question is how production ready is it. And
also
On 28 Mar 2012, at 07:44, Guillaume Lelarge wrote:
> On Tue, 2012-03-27 at 18:51 -0700, leaf_yxj wrote:
>> create one function to let other user execute vacuum command. got such an
>> error. Please help. Thanks. Regards . Grace
>>
>> rrp=> create function vacuum_f ( tablename char(100))
On 18 Oct 2011, at 20:17, Tom Lane wrote:
> =?ISO-8859-1?Q?Fr=E9d=E9ric_Rejol?= writes:
>> I created a custom CAST to cast from one table type to another.
>> pg_dump does not include my custom CAST.
>
> Hmm. The reason for that is that the table types aren't considered
> dumpable objects. I s
