x error at or near "window"
LINE 40: tablename := window.atablename;
The problem is with the variable name window; once I changed it things worked
fine. Now, Window is supposed to be a reserved word, so I am not necessarily
expecting it to work any more, but this code works fine in
On Saturday 16 January 2010 14:02:16 Tom Lane wrote:
> "Robert Treat" writes:
> > I added --disable-largefile to configure after getting the following
> > error during "make install"
> >
> > access/transam/xlog.o: In function `XLogFileClose':
&g
The following bug has been logged online:
Bug reference: 5283
Logged by: Robert Treat
Email address: xzi...@users.sourceforge.net
PostgreSQL version: 8.4.2
Operating system: Slackware Linux 2.6.23.14-grsec
Description:Missing "base/1/ON" file during init
The following bug has been logged online:
Bug reference: 4940
Logged by: Robert Treat
Email address: xzi...@users.sourceforge.net
PostgreSQL version: 8.3.7
Operating system: Linux 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008
x86_64 x86_64 x86_64 GNU/Linux
Description
The following bug has been logged online:
Bug reference: 4929
Logged by: Robert Treat
Email address: xzi...@users.sourceforge.net
PostgreSQL version: 8.3.1
Operating system: Linux 2.6.18-53.1.14.el5 #1 SMP x86_64 GNU/Linux
(Centos)
Description:Corrupted pg_class
On Tuesday 16 December 2008 15:40:17 robert treat wrote:
> The following bug has been logged online:
>
> Bug reference: 4585
> Logged by: robert treat
> Email address: xzi...@users.sourceforge.net
> PostgreSQL version: 8.3.x
> Operating system: solari
The following bug has been logged online:
Bug reference: 4585
Logged by: robert treat
Email address: xzi...@users.sourceforge.net
PostgreSQL version: 8.3.x
Operating system: solaris/linux
Description:out parameter name cuases disruption in custom
aggregate?
Details
On Monday 11 August 2008 21:38:38 Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > the second function takes a uuid, looks up an integer representation, and
> > then calls the first function. whenever I run it, I get the following
> > error:
> >
|
Indexes:
"rollup_matrix_numeric_5m_pkey" PRIMARY KEY, btree (rollup_time, sid,
name) CLUSTER
the full code for the int version of the function can be found at
https://labs.omniti.com/trac/reconnoiter/browser/trunk/sql/reconnoiter_ddl_dump.sql#L402
--
Robert Treat
Build A B
re-directing wayward bug report...
-- Forwarded Message --
Subject: BUG #4235: docu wrong for sqlerrmc[70]
Date: Thursday 12 June 2008
From: "Michael Enke" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
The following bug has been logged online:
Bug reference: 4235
Logged b
On Thursday 30 August 2007 21:15, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > pagila=# select to_date('05 December 2000', 'DD Month ');
> > to_date
> > ---
> > 0001-12-05 BC
> > (1 row)
> >
> &
27;t imagine that's expected behavior bug?
oh,
pagila=# select version();
version
-
PostgreSQL 8.2.4 on i386-pc-solaris2.10, compiled by cc -Xa
(1 row)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} Postgr
On Thursday 02 November 2006 17:48, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > pagila=# select to_date('3232098', 'MM/DD/');
> > to_date
> > ---
> > 4568-06-26 BC
> > (1 row)
>
> to_date&#x
anguage;
17:10 < AndrewSN> xzilla: arguably all of to_date, the date->timestamp cast
and timestamp_out are broken
17:11 < xzilla> AndrewSN: ok, i could see that :-)btw, if i do create
table t2 as select * from t1 i now have a table with the bad
timestamp th
The following bug has been logged online:
Bug reference: 2452
Logged by: Robert Treat
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Fedora Core 4
Description:Error w/ pg_restore and blobs
Details:
[EMAIL PROTECTED] ~]# time pg_restore
To my knowledge it hasn't, at least no one has asked me for the sample
database.
Robert Treat
On Thursday 26 January 2006 17:42, Bruce Momjian wrote:
> Has this been researched. Josh posted he thought it was an optimizer
> bug, but I haven't seen anyone investiga
en columns that are not
primary keys, contain duplicate values (so they are aren't unique), and
involves left joining subqueries. It doesn't seem to follow that it
would always reduce to 1 row quite so easily.
Robert Treat
On Wed, 2006-01-18 at 16:11, Bruce Momjian wrote:
>
> Ma
chopped up test database which can reproduce the query issues off list
should someone want to walk through the pg code to investigate. TIA
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP
since I've confirmed this behavior on Slackware Linux 10
with psql version 8.1beta1 and there does seem to be something wrong with the
above situation (perhaps the man page needs to be reworded?)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Friday 16 September 2005 09:00, Michael Fuhr wrote:
> On Fri, Sep 16, 2005 at 06:02:14AM +0100, Robert Treat wrote:
> > PostgreSQL version: 8.1beta1
> >
> > When doing SHOW or SHOW a none of the autovacuum
> > settings come up.
>
> Are you sure you'r
The following bug has been logged online:
Bug reference: 1885
Logged by: Robert Treat
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1beta1
Operating system: FC2
Description:SHOW autovacuum settings tab completion broken
Details:
When doing SHOW or SHOW a
ll update with the next site build. Thanks for the report.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Redirecting this to pgsql-bugs where it belongs.
Robert Treat
On Wed, 2005-08-17 at 01:29, Lee Hyun soon wrote:
> From: "Lee Hyun soon" <[EMAIL PROTECTED]>
> To: pgsql-bugs@postgresql.org
> Date: Wed, 17 Aug 2005 05:36:23 +0100 (BST)
> Subject: BUG #1826: pgsql odbc
On Monday 07 March 2005 16:22, Robert Treat wrote:
> On Sunday 06 March 2005 15:25, Hashem Masoud wrote:
> Thanks for the report! Attached patch fixes this and 3-4 other typos as
> well.
Hashem has kindly pointed out a few more typos in the FAQ that I have added
in, please apply t
t element i.
>
>
> (inteter) should be (integer)
>
Thanks for the report! Attached patch fixes this and 3-4 other typos as well.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: FAQ_DEV.html
;
...
$ systcl -w kernel.shmmax=134217728
$ systcl -w kernel.shmall=2097152
systcl is wrong sysctl notStefan
-------
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: runtime.sgml
=
when you do \h CREATE CON
you get CREATE CONVERSION instead.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
j
(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
---
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Sunday 31 October 2004 10:16, Robert Treat wrote:
> pgsql running on port 5480, connect to t\echo :PORTemplate1 as non-superuser
> "phppgadmin" who does not have createdb privileges. attempt to run a script
> that creates a database "phppgadmin" and then do a \conne
ide the script, or recall that it needs to connect on 5480
after failure.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
On Thu, 2004-08-26 at 09:08, Gaetano Mendola wrote:
> Robert Treat wrote:
>
> > On Thu, 2004-08-26 at 04:23, Gaetano Mendola wrote:
> >
> >>Tom Lane wrote:
> >>
> >> > Stephan Szabo <[EMAIL PROTECTED]> writes:
> >> >
> &g
ee with Tom that 8.0 does seem like the best time to make such a
change and I'd like to see this put up to a vote since I have _never_
seen anyone argue the case that the current functionality is
preferable. I'm sure some will argue that they don't want to make the
change now that we are alre
gt; "ALTER SCHEMA foo OWNER TO bla" if you're a super user.
>
And using 8.0... I saw that but was looking for a 7.4 solution...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)-
this has not happened yet, partly because we are
> not sure of all the consequences.
>
was just looking at this this morning. is there anyway to change
ownership of a schema? i couldn't find one and thought i'd ask before
whacking on the system tables.
Robert Treat
--
-
> The binaries must be linked with pthread (-lpthread).
>
Can you take a look at the thread below and report back if that fixes your
problem? http://archives.postgresql.org/pgsql-hackers/2004-08/msg00525.php
--
Robert Treat
Build A Better Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
nction's return type
ERROR: pg_atoi: error in "one": can't parse "one"
so ISTM that your example is certainly a deficiency if not a bug.
hmm..examples above on 7.3, which didnt support check constraints, so this is
potentially different on 7.4.
Robert Treat
On Thursday 0
I believe this to be fixed. If you see any further problems please
report them.
Robert Treat
On Fri, 2003-03-14 at 11:26, [EMAIL PROTECTED] wrote:
> Daniel Quaroni ([EMAIL PROTECTED]) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short
[EMAIL PROTECTED] rms_db]$ cal 9 1752
September 1752
Su Mo Tu We Th Fr Sa
1 2 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
I guess adding 1 day to 1752-09-02 should give us 1752-09-14, but your
right, it gives us 1752-09-03.
Forwarding this to -bugs
Robert Treat
On Sun
On Mon, 2002-12-16 at 18:53, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > "this is broken on so many levels..."
>
> The issue here is that the second transaction has already set its
> snapshot when it enters the function body; so even though i
le mode, the second
function would, upon attempt to update the first record, see that the
record was already updated, and throw a "ERROR: Can't serialize access
due to concurrent update", which could then be dealt with accordingly.
As it stands now we have a bastardization of the t
40 matches
Mail list logo
