entirely.
Of course you are superuser when you review such logs, but I wouldn't
usually want the db connection from the application to have to run as
superuser if I could help it... especially not a web application.
Regards,
Andrew McMillan.
---
On Thu, 2003-02-06 at 22:26, Yaniv Hamo wrote:
> Hi,
> I noticed that Postgres issues a fatal error when given a quoted name of
> table or column. This is a problem in secured cgi scripts, which quote
> everything they get from the user, to avoid malicious users from trying to
> execute SQL comma
On Tue, 2003-02-04 at 21:00, [EMAIL PROTECTED] wrote:
> venu ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> CAP letters
>
> Long Description
> i want to port SQL server database to Postgresql,while porting i am
> encout
On Thu, 2002-06-06 at 01:54, Sam Liddicott wrote:
> >
> > It would be interesting to see the 'vacuum full analyze'
> > results for the
> > system tables in that DB, although perhaps less interesting while you
> > are running your current solution - maybe a comparison would be
> > worthwhile.
>
On Wed, 2002-06-05 at 21:02, Sam Liddicott wrote:
> >
> > When did you last do a vacuum? If you are adding and
> > dropping temporary
> > tables a lot, perhaps you should vacuum pg_class and
> > pg_attribute often
> > as well.
>
> I do a vacuum analyse every night on that whole DB, cron logs
On Fri, 2002-05-31 at 22:28, Sam Liddicott wrote:
> And when I do drop a table CPU usage goes to 99% on one CPU.
When did you last do a vacuum? If you are adding and dropping temporary
tables a lot, perhaps you should vacuum pg_class and pg_attribute often
as well.
Regards,
On Wed, 2002-05-29 at 01:41, Tom Lane wrote:
>
> > Is it a good idea to provide an example (such as the above), or should I
> > just try and describe the behaviour?
>
> Examples are generally good things ...
OK, the attached documentation patch provides some simple examples of
use of tablename
On Tue, 2002-05-28 at 04:59, Tom Lane wrote:
> Andrew McMillan <[EMAIL PROTECTED]> writes:
> > Reading between a few lines I got the impression that the manual
> > suggested something like:
> > CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
> > When I f
I recently referred to the manual (section 23.3) to work out how to
write a PL/PgSQL function that accepted a row as a parameter.
Reading between a few lines I got the impression that the manual
suggested something like:
CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
When I finally g
On Sat, 2002-03-02 at 04:16, Thomas Lockhart wrote:
> > timestamp(timestamp('a timestamp)) no longer works
> > I do this reasonably often in my code by way of being paranoid
> > that I might have a date, or a time, where I for sure _really_
> > want it to be a timestamp...
> > pcnz=# select timest
Andrew.
--
_____
Andrew McMillan, e-mail: [EMAIL PROTECTED]
Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington
Me: +64 (21) 635 694, Fax: +64 (4) 499 5596, Office: +64 (4) 499 2267
---(end of broadcast)
with IN ( ... ) and the use of indexes - you would
get better results using EXISTS.
Cheers,
Andrew.
--
_
Andrew McMillan, e-mail: [EMAIL PROTECTED]
Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington
Me: +64 (21) 635 694, Fax: +64 (4) 499 5596, Office: +64 (4) 499 2267
0
> , not 7.0
>
> No file was uploaded with this report
>From the line break in the "should be 7.0
, not 7.0" I wonder if it isn't a CRLF vs LF problem?
Regards,
Andrew.
--
__
solution.
something like:
set CENTURY_WINDOW TO '1980';
Would be nicest.
Regards,
Andrew.
--
_____
Andrew McMillan, e-mail: [EMAIL PROTECTED]
Catalyst IT Ltd, PO Box 10-225
{"not","other","full"}
{"not","other","full"}
(2 rows)
testing=# update t1 set c1[2] = 'strange', c1[3] = 'notfull';
UPDATE 2
testing=# select * from t1;
c1
--
{"not","strange","full"}
{"not","strange","full"}
(2 rows)
--
So it looks like UPDATE is silently ignoring second and subsequent
references to the same array variable. In most cases...
A good workaround muight be for you to use the '{"blah", "blah",
"blah"}' syntax for updating the array, although it's a pretty messy
syntax.
Cheers,
Andrew.
--
_
Andrew McMillan, e-mail: [EMAIL PROTECTED]
Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington
Me: +64 (21) 635 694, Fax: +64 (4) 499 5596, Office: +64 (4) 499 2267
logging except that whenever I do that I tend to run out of disk space
:-(
Thanks,
Andrew.
--
_
Andrew McMillan, e-mail: [EMAIL PROTECTED]
Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington
Me: +64 (21) 635 694, Fax: +64 (4) 499 5596, Office: +64 (4) 499 2267
16 matches
Mail list logo
