There was a review of a DB book on Slashdot some time ago, and parts of
the book said that SELECTs are always safe since it never modifies
anything in the db :)
This proves it wrong:
Try this (7.4Devel but should work on 7.3): Granting to several users.
-- pg_grant(priviledge, table, user)
cre
The best autovacuum is in 7.4devel, soon to go beta, in the /contrib
directory.
---
Mendola Gaetano wrote:
> Hi,
> I used to install postgres 7.3.3 from RPM,
> today I needed to take a look at pg_utovacuum but I didn't
>
Hi,
I used to install postgres 7.3.3 from RPM,
today I needed to take a look at pg_utovacuum but I didn't
find it ?
Should I download it from somewhere else ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our exte
Thanks
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
I inadvertently used my userid instead of the one I should have used to initialize the
db. How can I recover/remove this error and
get back to a clean initialization point?
Thanks
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Hi,
I used to install postgres 7.3.3 from RPM,
today I needed to take a look at pg_utovacuum but I didn't
find it ?
Should I download it somewhere else ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe comm
=?ISO-8859-1?Q?Dennis_Bj=F6rklund?= <[EMAIL PROTECTED]> writes:
> On Sun, 3 Aug 2003, Tom Lane wrote:
>> I added code to inline_function to stop inlining if a parameter
>> expression to be substituted multiple times has cost greater than
>> 10*cpu_operator_cost (which roughly means that it contains