On Sun, Jun 30, 2013 at 09:31:18PM -0400, Michael Orlitzky wrote:
> (why do I get the feeling nobody is going to check out the repo):
Probably because you're asking random strangers on the Internet to
help you solve their problems, and many of such strangers have other
things to do than go somewhe
On 06/30/2013 09:12 PM, Andrew Sullivan wrote:
>
> If you want "easy", then just give different databases per user. If
> you want complicated, you need an administrator; yes, that needs to be
> in some sense under the control of the host. We have roughly 40 years
> of experience with these thing
On 06/30/2013 08:45 PM, David Johnston wrote:
>
> So PostgreSQL is only useful, for shared hosting, when the only permissible
> access is via vendor-supplied resources (APIs, administrators, etc...)?
>
I'm not sure I understand, but I don't think that's what I'm saying. I
want my customers and c
On 06/30/2013 07:06 PM, John R Pierce wrote:
> On 6/30/2013 12:46 PM, Michael Orlitzky wrote:
>> We use Postgres for shared hosting; i.e. what most people use MySQL for.
>> The biggest headache for us so far has been that we're unable to get
>> group permissions set up effectively so that different
On Sun, Jun 30, 2013 at 05:45:47PM -0700, David Johnston wrote:
> So PostgreSQL is only useful, for shared hosting, when the only permissible
> access is via vendor-supplied resources (APIs, administrators, etc...)?
No, of course not, especially in light of recent improvements. But
any finely-gr
John R Pierce wrote
> On 6/30/2013 12:46 PM, Michael Orlitzky wrote:
>> We use Postgres for shared hosting; i.e. what most people use MySQL for.
>> The biggest headache for us so far has been that we're unable to get
>> group permissions set up effectively so that different groups of
>> customers,
On 6/30/2013 12:46 PM, Michael Orlitzky wrote:
We use Postgres for shared hosting; i.e. what most people use MySQL for.
The biggest headache for us so far has been that we're unable to get
group permissions set up effectively so that different groups of
customers, admins, apaches, etc. can access
We use Postgres for shared hosting; i.e. what most people use MySQL for.
The biggest headache for us so far has been that we're unable to get
group permissions set up effectively so that different groups of
customers, admins, apaches, etc. can access/modify the data they need,
without manual interv
On Jun 30, 2013 7:07 PM, "bhanu udaya" wrote:
>
>
> I almost used every option ; upper, posix, gist, gin, citext, etc.
feature of the postgres to get the query most optimal.. If a particular
query is taking 1 + second for one user/thread, then for many users
accessing it concurrently would take l
Create database with UTF8 character with Collation Posix.
Also, modified the table column as below:
alter table tableA alter column colA type text COLLATE POSIX
create Index btree index on ColA Collate POSIX
Use the query lower(colA) like 'b%'
The results seems promissing. But, would like to do mor
I almost used every option ; upper, posix, gist, gin, citext, etc. feature of
the postgres to get the query most optimal.. If a particular query is taking 1
+ second for one user/thread, then for many users accessing it concurrently
would take lot of resources and the performance would be d
I almost used every option ; upper, posix, gist, gin, citext, etc. feature of
the postgres to get the query most optimal.. If a particular query is taking 1
+ second for one user/thread, then for many users accessing it concurrently
would take lot of resources and the performance would be dropp
12 matches
Mail list logo
