incremental pg_dump's onto tmpfs. Advantage there is that the
dump iteslf has effectively no write I/O overhead: you can dump to
tmpfs and then [bg]zip to stable storage w/o beating up the disks,
which becomes a real problem with comodity-grade hardware.
--
Steven Lembark
type.html>
[2] <http://www.postgresql.org/docs/9.4/static/rangetypes.html>
[3] <http://stackoverflow.com/questions/28017891/postgres-custom-range-type>
[4]
<http://grokbase.com/t/postgresql/pgsql-general/128355kvhc/range-types-in-9-2>
[5]
<https://wiki.postgresql.org/wiki/Working_wit
map { $1::text }" in plsql.
*/
$$
;
or is there something built in that I have missed?
Note: Performance will not be an issue here as the table is not
updated all that frequently.
Any references appreciated.
--
Steven Lembark 364
er, tuning the database to accomodate them is a
better bet.
It would also be worth checking whether the I/O was entirely due
to sequential reads or may have been swapping. procinfo, vmstat,
or just top can tell you about that.
--
Steven Lembark
operator does not exist: retired_date => retired_date at line 56.
seems to indicate that retired date cannot be
cast to itself?
This also seems odd since passing in timestamps
with other queries seems to work happily and
perform the convrsion automatically.
thanx
--
Steven Lembark
th=164)
Filter: (foo_id = 1)
-> Seq Scan on foo_5 foo (cost=0.00..15.25 rows=2 width=164)
Filter: (foo_id = 1)
-> Seq Scan on foo_6 foo (cost=0.00..15.25 rows=2 width=164)
Filter: (foo_id = 1)
-> Seq S
char argument (requires
bytea).
If there is an example in the doc's I'd appreciate
a link to it.
thanks
--
Steven Lembark85-09 90th St.
Workhorse Computing Woodhaven, NY, 11421
lemb...@wrkhors.com
ll gave me the
warnings.
thanx
--
Steven Lembark85-09 90th St.
Workhorse Computing Woodhaven, NY, 11421
lemb...@wrkhors.com +1 888 359 3508
--
Sent via pgsql-general mailing list (pgsq
> Which "warnings" are you talking about? I thought you said you had
> plain SQL working OK, but were struggling to pass parameters containing
> UTF-8 encoded characters.
>
> Are you sure that your Perl code is passing the string encoded as UTF8?
Excellent point: Perl will only pass through the
