> I am just beginning to investigate schemas, and have run into a
> problem. Searching the mailing lists and documentation doesn't help.
>
> This is 7.3.3 on Linux, kernel 2.4.21, good ole Slackware, compiled
> from source.
>
> Two users, JoeBob and MaryJo. JoeBob has schema xyzzy with table
> pl
[EMAIL PROTECTED] writes:
> joebob=> select * from xyzzy.plugh;
> ERROR: xyzzy: permission denied
> It sure looks like the schema itself is invisible to MaryJo, but
> MaryJo can run \dt xyzzy.* perfectly fine.
You need to grant USAGE permission on the schema to MaryJo.
We've seen this mi
Andreas Lehrbaum <[EMAIL PROTECTED]> writes:
> Is it possible in _any_ way to control the order of the rows passed to an
> aggregate function?
For simple aggregation you can do
SELECT myagg(col) FROM (SELECT col FROM ... ORDER BY foo) ss;
If you wanted to group, you could try
SELECT gcol, myag
On Sun, 2003-06-22 at 15:47, Bruce Momjian wrote:
> Ron Johnson wrote:
> > On Sun, 2003-06-22 at 12:46, Bruce Momjian wrote:
> > > Ron Johnson wrote:
> > > > On Sun, 2003-06-22 at 00:05, Bruce Momjian wrote:
> > > > > Bruce Momjian wrote:
> > > > > >
> > > > > > Reading the subject, "creepy ... da
I think most people would agree that a large part of MySQL's audience has come from
the bundling of MySQL libraries with PHP. Getting PostgreSQL to fill this void would
be a very positive development.
If concerns about licensing are a major driver here, I would think that PostgreSQL's
simple B
Kevin Jacobs <[EMAIL PROTECTED]> writes:
> Attached is a patch that removes all of the RExec code from plpython from
> the current PostgreSQL CVS. In addition, plpython needs to be changed to an
> untrusted language in createlang.
I am inclined to rename plpython to plpythonu, by analogy to pltcl
Ron Johnson wrote:
> > #
> > # (initialized by initdb -- may be changed)
> > LC_MESSAGES = 'C'
> > LC_MONETARY = 'C'
> > LC_NUMERIC = 'C'
> > LC_TIME = 'C'
>
> As long as it's overridable by a "masking set statement", does
> it matter? Well, it probably does, for consisten
Bruce Momjian wrote:
Josh Berkus wrote:
Joe,
> Interesting thread (php-dev subj: removing bundled libmysql):
>http://marc.theaimsgroup.com/?l=php-dev&m=105621066832429&w=2
>
> I particularly liked this post:
> (http://marc.theaimsgroup.com/?l=php-dev&m=105621207500778&w=2)
Boy, Monty's making
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Interesting thread (php-dev subj: removing bundled libmysql):
> http://marc.theaimsgroup.com/?l=php-dev&m=105621066832429&w=2
Hoo boy. Did you catch the part about
>> and the MySQL 3.2.23
>> library can't connect to MySQL 4.1 servers, rendering it brok
> To clearify, we need to encourage the PHP developer community to
> encourage the PHP user community to switch to PostgreSQL.
>
> What I'm worried about is exactly the people who adopted MySQL already.
> The change to another database will be painfull no matter what. How many
> of them will be
On Sun, 22 Jun 2003 [EMAIL PROTECTED] wrote:
> MySQL also does case independent text comparisions, and apparently ONLY
> case-insensitive comparisons.
Is this a good thing? Doesn't sound like it to me, but figured I'd ask :)
---(end of broadcast)
> I know it took me a while to convince the CIO on the project I'm working
> on that PostgreSQL was an improvement over MySQL. He's slowly coming
> around as I start to show him what I am doing with the much richer
> PostgreSQL feature set, but the performance of 7.3 compared to MySQL is
> likel
On Sun, Jun 22, 2003 at 10:19:20PM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Interesting thread (php-dev subj: removing bundled libmysql):
> > http://marc.theaimsgroup.com/?l=php-dev&m=105621066832429&w=2
Note the comment on
http://marc.theaimsgroup.com/?l=php-dev&m=10
> On Sun, 22 Jun 2003 [EMAIL PROTECTED] wrote:
>
> > MySQL also does case independent text comparisions, and apparently ONLY
> > case-insensitive comparisons.
>
> Is this a good thing? Doesn't sound like it to me, but figured I'd ask :)
I think it is a classic case of thinking 'small'. :-)
Th
> Whoa, something's not right. Could you please send along an EXPLAIN
> ANALYZE after doing a VACUUM ANALYZE of your query that's taking 3-4x
> longer?
As luck would have it, I just finished the latest 'emergency' part of
the project, so I may have a day or so to play with this before the
CIO
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Better hurry. Sterling Hughes is proposing to enable SQlite support by
> default; that move could be bad for the lobbying of activating Pg
> support.
SQlite? Sure, give it a try. (I was slightly astonished to compare
these two pages:
http://www.hwac
On Sun, 22 Jun 2003 23:57:10 -0400 Tom Lane <[EMAIL PROTECTED]> wrote:
> I'd be happy if PHP would adopt a database-neutral stance, ie, nothing
> in particular bundled into their core distribution. That might not be
> compatible with their project goals though. Anyone have a feeling about
> how i
Hi,
3.2.23 was a LONG time ago. One thing I like about mysql is that they are
constantly making major improvements. I have asked this before, where is
Replication with PostgreSQL? If there was a system that could handle more
than one master without hacking, I would seriously look into switching t
> > Whoa, something's not right. Could you please send along an
> > EXPLAIN ANALYZE after doing a VACUUM ANALYZE of your query that's
> > taking 3-4x longer?
>
> As luck would have it, I just finished the latest 'emergency' part
> of the project, so I may have a day or so to play with this before
On Sun, Jun 22, 2003 at 11:57:10PM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Better hurry. Sterling Hughes is proposing to enable SQlite support by
> > default; that move could be bad for the lobbying of activating Pg
> > support.
>
> SQlite? Sure, give it a try.
On Sun, 22 Jun 2003 [EMAIL PROTECTED] wrote:
> > On Sun, 22 Jun 2003 [EMAIL PROTECTED] wrote:
> >
> > > MySQL also does case independent text comparisions, and apparently ONLY
> > > case-insensitive comparisons.
> >
> > Is this a good thing? Doesn't sound like it to me, but figured I'd ask :)
>
>
On Sun, 22 Jun 2003, Eric Frazier wrote:
> constantly making major improvements. I have asked this before, where is
> Replication with PostgreSQL?
Replication for PostgreSQL has been available, and in production use, for
at least two years now ... the .ORG registry is using eRServer ... there
w
Sterling Hughes <[EMAIL PROTECTED]> writes:
> Many sites don't require a relational database system.
Agreed. If SQlite gets the job done for some folk, then that's the
tool they ought to use. I was just a tad bemused by the apparent
claim that it could be considered a substitute for Postgres (or
On 6/22/03 10:57 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Better hurry. Sterling Hughes is proposing to enable SQlite support by
>> default; that move could be bad for the lobbying of activating Pg
>> support.
>
> SQlite? Sure, give it a try. (
> > Personally, if I want case insensitivity, I'll WRITE IT INTO THE CODE,
> > but I can see how some people might think that 'NOLAN', 'Nolan' and
> > 'nolan' should be considered as the same data.
>
> Oh, you mean like "SELECT * FROM table WHERE field ~* 'nolan';"?
No, I mean as in "SELECT * FRO
[ Please stop cross posting emails between mailing lists! ]
> > > Personally, if I want case insensitivity, I'll WRITE IT INTO THE CODE,
> > > but I can see how some people might think that 'NOLAN', 'Nolan' and
> > > 'nolan' should be considered as the same data.
> >
> > Oh, you mean like "SELECT
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Jeffrey W. Baker wrote:
> On Mon, 2003-06
> Is it
> desiarable to default postgresql.conf datestyle to match the locale?
>
> #
> # Locale settings
> #
> # (initialized by initdb -- may be changed)
> LC_MESSAGES = 'C'
> LC_MONETARY = 'C'
> LC_NUMERIC = 'C'
> LC_TIME = 'C'
Another JPY 2
On Fri, Jun 20, 2003 at 11:14:02PM -0400, Tom Lane wrote:
> > There are some, but I still disagree. The biggest advantage of
> > PostgreSQL in my opinion has always been that it's a community project
> > and not driven by some commercial interests.
>
> These are not mutually exclusive. Each devel
On Sat, Jun 21, 2003 at 11:40:52AM -0300, The Hermit Hacker wrote:
> I have no doubt that some of those features were 'pushed to the top of the
> TODO list' due to their business case, but I can't think of any that were
> against teh desires of the community ... were there?
No, there were definite
30 matches
Mail list logo
