On Tue, 2017-07-04 at 17:55 -0400, Stephen Frost wrote:
> Greetings,
>
> * hvjunk (hvj...@gmail.com) wrote:
> > I’ve previously done ZFS snapshot backups like this:
> >
> > psql -c “select pg_start_backup(‘snapshot’);”
> > zfs snapshot TANK/postgresql@`date ‘+%Ymd’`
> > psql -c “select * from pg
On Mon, 2016-03-21 at 15:58 +0100, Alexander Farber wrote:
> Thanks for your replies.
>
>
> While I use "\i" regularly I just didn't realize it would be suitable
> here as well :-)
>
\ir migth be a better option for a bundle of scripts, related to main
script (words.sql in your case), not to cwd
ple might be more complicated than one
column update, but looking at your fun, it scared me, i mean, your fun
updates every one row in table anyway, so why so many times with
additional scan to check loop condition? it gets worse if there is no
partial index where batch_number is null.
regards, mariusz
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
milar to Microsoft's SQL Server. Sybase also declares deep cooperation with
Novell (SuSE distribution). I don't think Oracle does not bother with this.
Regards,
Mariusz Czułada
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ECT * FROM sharp_p1;
ERROR: ON SELECT rule may not use OLD
Is it my mistake, or some feature I did not find in the docs?
regards,
Mariusz
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org
a' in
'user_xxx_schema' preserving of course names, constraints, triggers, etc.
Optionally it could also copy table contents (but this is not very
important).
Or is there any other (relatively simple and safe) way do do this *inside* a
stored function (pl/pgsql)
