wooo, thanks for all of your advice
it seems to be ok now!
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Help-How-to-start-the-server-tp5756725p5757271.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing li
On 5/21/13 2:41 PM, Bruce Momjian wrote:
> I have thought about this and there are potentially several options
> specified to pg_upgrade that could be passed into scripts:
>
> -O, --new-options=OPTIONS new cluster options to pass to the server
> -P, --new-port=NEWPORTnew cluster po
Sorry, I wasn't sure what list I should be sending this question to...
I have a multi-tenant-like application. We have a fields tree that we
call a template, with something like this:
fields(id, parent_id, name)
And several other related tables. Since we started to support multiple
templates
We re-tested these settings a few times after our initial test and realized that the execution time I posted was shewed, because the execution plan was cached after the initial run. Subsequent executions ran in a little over a second.
There ended up being no significant saving by setting these para
On 23 May 2013 15:33, Thom Brown wrote:
> On 23 May 2013 10:15, Keith Fiske wrote:
>> Client reported an issue where it appears a foreign key has been violated
>>
>> prod=#\d rma_items
>> [snip]
>> rma_items_rma_id_status_fk" FOREIGN KEY (rma_id, rma_status) REFERENCES
>> rmas(id, status) ON UPDA
On Wed, May 29, 2013 at 09:42:12AM -0400, Peter Eisentraut wrote:
> On 5/21/13 2:41 PM, Bruce Momjian wrote:
> > I have thought about this and there are potentially several options
> > specified to pg_upgrade that could be passed into scripts:
> >
> > -O, --new-options=OPTIONS new cluster op
On Wed, May 29, 2013 at 9:58 AM, Rodrigo Rosenfeld Rosas wrote:
> I know I could use a trigger, or some check constraint maybe, to ensure
> the field exists upon insert (or update), but I can't ensure the database
> will become inconsistent in case I remove a mapped field from the other
> schema.
Em 29-05-2013 12:51, Vick Khera escreveu:
On Wed, May 29, 2013 at 9:58 AM, Rodrigo Rosenfeld Rosas
mailto:rr.ro...@gmail.com>> wrote:
I know I could use a trigger, or some check constraint maybe, to
ensure the field exists upon insert (or update), but I can't
ensure the database w
Greetings:
I've just joined this list having heard of this database only thirty minutes
ago. Apparently my new assignment will have me working on / developing a local
solution using this database for the backend.
My name is Jim Corbett and I hail from Ottawa Canada where I work for the
federal
James,
* Corbett, James (james.corb...@cra-arc.gc.ca) wrote:
> My name is Jim Corbett and I hail from Ottawa Canada where I work for the
> federal government as a Java Web developer.
Good to have you; unfortunately you just missed PgCon, which was held at
the University of Ottawa last week. The
This is just a guess (I haven't dug into the low-level page/disk access
Postgres code for Large Objects yet but if I'm right, the LO-based project
I'm working on will likely face the same issues you're seeing), but LOs
enjoy transactional behavior just like anything else (as far as I can tell
from
Hi everyone;
I have put together a basic framework for integrating PostgreSQL stored
procedures into Perl objects. For those who have followed my blog, this
implements the stored procedure mapping systems we use in LedgerSMB for
more general users.Interfaces have been generalized and so they
Hello,
I have a database in which I want to grant permission so that when ANY
table is created by a member of role_a SELECT access is granted on it to
ALL members of role_b.
I had thought that:
ALTER DEFAULT PRIVILEGES FOR ROLE role_a GRANT SELECT ON TABLES TO role_b;
or
ALTER DEFAULT PRIV
* James Sewell (james.sew...@lisasoft.com) wrote:
> Is there a way to achieve this? I want role_a to maintain this level of
> access as new tables are created (all creators will be in role_b).
Sadly, no. It's exactly what I was originally hoping for with the
DEFAULT PRIVILEGES capability, but it'
Hi,
I am process of porting from sybase to postgresql. Is there syntax equivalent
of the TRIGGER EVENT Statement (Please see the sybase help for trigger event
below) in Postgresql. NOTE the TRIGGER EVENT in sybase could be used to trigger
an user defined event. I am not seeing any similar synta
Sajeev Mayandi wrote:
> Hi,
>
> I am process of porting from sybase to postgresql. Is there syntax equivalent
> of the TRIGGER EVENT Statement (Please see the sybase help for trigger event
> below) in Postgresql. NOTE the TRIGGER EVENT in sybase could be used to
> trigger an user defined event.
16 matches
Mail list logo