On 7/02/2012 3:48 AM, Tom Lane wrote:
Pat Heuvel writes:
On 6/02/2012 4:39 AM, Tom Lane wrote:
What exactly happens when you try to reindex pg_largeobject?
ERROR: could not create unique index "pg_largeobject_loid_pn_index"
DETAIL: Table contains duplicated values.
Could be worse. What yo
> Il giorno 08/feb/2012, alle ore 11:25, Marti Raudsepp ha
> scritto:
>
>> On Wed, Feb 8, 2012 at 01:17, 84.le0n <84.l...@gmail.com> wrote:
This is a bit ugly, but you could write the function yourself in the
PL/pgSQL procedural language, which is enabled by default in Postgres
9
<<< text/html; charset="utf-8": Unrecognized >>>
<>
I'm wondering about my CREATE ROLE statements for PostgreSQL. I guess
I don't know if there's an official answer but I feel like I'm
entering a lot of redundant privileges to a role for example:
CREATE ROLE tom NOINHERIT LOGIN SUPERUSER CREATEDB CREATEROLE REPLICATION;
CREATE ROLE
My question is
mgo...@isstrucksoftware.net wrote:
> We need to ensure that our data is in upper case only in the db. Is there a
> easy way to do this via a function without having to name each column
> separately?
You can define a TRIGGER for such tasks (befor insert or update), but
you have to name each colu
Carlos Mennens writes:
> My question is do I need to specify CREATEDB & CREATEROLE if I'm
> already granting the SUPERUSER privilege?
No, not really. The point of those options is to grant privileges to
roles that aren't superuser.
> Also when I generate a new role, is there any difference betw
mgo...@isstrucksoftware.net wrote:
> Andres,
>
> Darn, I was hoping to not need to do one for each table. I was hoping that
> using %RowType might work.
1st, please answer to the list, not to me, okay?
2nd, please don't top-posting, quote below. It's hard to read
3rd, i understand your problem
Le mardi 07 février 2012 à 10:30 +0200, Achilleas Mantzios a écrit :
> On Τρι 07 Φεβ 2012 07:05:00 John R Pierce wrote:
> > On 02/03/12 5:53 PM, Rodrigo E. De León Plicet wrote:
> > > Author's followup:
> > >
> > > http://drcoddwasright.blogspot.com/2012/02/damn-you-damocles.html
> >
> > his link
I got an alert from check_postgres.pl today on a long-running query on
our production database, but our PostgreSQL 8.4.9 server log, which is
configured to log queries over 5 seconds long
("log_min_duration_statement = 5000") does not show the query.
check_postgres.pl showed:
Date/Time: Wed Feb 8
