When grilled further on (Sun, 26 Jun 2005 15:18:47 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > This doesn't seem right:
>
[ snip embarrassing mistake ]
>
> Why doesn't it seem right? You're as
This doesn't seem right:
CREATE VIEW inci AS
SELECT date, inci_id, protocol, a.ip_addr, b.ip_addr, spt, dpt
FROM (SELECT addr_id, ip_addr FROM addrs) AS a
JOIN incident ON incident.source_addr_id = a.addr_id
JOIN (SELECT addr_id, ip_addr FROM addrs)
AS b ON incident.de
When grilled further on (Sun, 27 Mar 2005 02:26:02 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
>
> We need to change the function APIs so that date2isoweek passes back
> some indication of which year it thought the week belongs to, and then
> isoweek2date must use that instead of the original
When grilled further on (Fri, 25 Mar 2005 08:28:58 + (GMT)),
"Dirk Raetzel" <[EMAIL PROTECTED]> confessed:
>
> The following bug has been logged online:
>
> Bug reference: 1563
> Logged by: Dirk Raetzel
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Opera
When grilled further on (Mon, 30 Aug 2004 11:31:12 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > While doing some daily processing, I ran across the following error:
>
> > ERROR: could not find a feasible split
When grilled further on (Thu, 4 Mar 2004 13:56:42 -0400 (AST)),
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> confessed:
> Some late dates give in some years wrong
> date_part('week')
>
> examples:
>
> select date_part('week', '2003-12-30'::date);
> date_part
> ---
> 1
> (1 row)
When grilled further on (Sat, 24 Jan 2004 15:54:07 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> > A custom Perl 5.6.1, DBI 1.30, DBD::Pg 1.22 script on Solaris 5.8.
> > Using pgsql client version 7.3.3. I'm thinking it may be related to
> > my forking? My program has a db connection, which
When grilled further on (Thu, 22 Jan 2004 22:19:44 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > What more information would you be looking for?
>
> Well, in the words of the old saw, if we knew what we were looking fo
When grilled further on (Thu, 22 Jan 2004 14:27:19 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > Description:message type 0x49 arrived from server while idle
>
> Hm. This would seem to have something to do with issuing empty quer
When grilled further on (Sun, 12 Oct 2003 13:06:25 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
>
> The two temp tables share a common parent?
Ops, forgot. Yes. "obs_root" (which is what the temp table inherits from), is
a persistent table. The temp table is used to filter data going into o
When grilled further on (Sun, 12 Oct 2003 13:06:25 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
>
> Can you get a backtrace from the errfinish call to confirm this theory?
Breakpoint 1, 0x081b4806 in errfinish ()
(gdb) bt
#0 0x081b4806 in errfinish ()
#1 0x081b5546 in elog_finish ()
#2 0x0
Hey folks,
Running 7.4b4 on a 2 processor SMP system:
PostgreSQL 7.4beta4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 (Mandrake
Linux 9.1 3.2.2-3mdk)
CREATE TEMP TABLE is being executed in two processes (same Perl/DBI script). It
occurs when the scripts are executed at the same time
When grilled further on (Sun, 05 Oct 2003 23:22:45 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
>
> so indeed everyone is waiting for this process:
>
> postgres 29304 20209 0 17:37 pts/400:00:00 postgres: robert tassiv
> 192.168.0.250 idle in transaction
Hmmm... Not
When grilled further on (Sun, 05 Oct 2003 20:34:15 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
>
> Almost certainly, that guy is holding the lock REINDEX wants. The
> VACUUM is probably backed up behind the REINDEX. If you want to
> convince me it's a deadlock, you'll need to exhibit pg_loc
I'm running 7.4b4 and ran into a little problem with my import and pg_autovacuum's
call of VACUUM.
PostgreSQL 7.4beta4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 (Mandrake
Linux 9.1 3.2.2-3mdk)
$ ./configure --with-tcl --with-openssl=/usr/include/openssl --with-CXX
--enable-syslog
Once upon a time (Thu, 25 Sep 2003 01:28:29 -0400)
Tom Lane <[EMAIL PROTECTED]> uttered something amazingly similar to:
> Robert Creager <[EMAIL PROTECTED]> writes:
> >> Seems like the correct behavior to me. When CONSTRAINT is given, the
> >> name is not opti
Once upon a time (Wed, 24 Sep 2003 21:10:53 -0700 (PDT))
Stephan Szabo <[EMAIL PROTECTED]> uttered something amazingly similar
to:
>
> On Wed, 24 Sep 2003, Bruce Momjian wrote:
>
> > Sent for user who is having trouble posting to bugs list:
>
> Seems like the correct behavior to me. When CONSTR
Hey,
Just wondering if the rule:
%.sql: %.sql.in
sed 's,MODULE_PATHNAME,$$libdir/$*g' $< >$@
is supposed to produce files like this:
CREATE OR REPLACE FUNCTION pgxml_parse(text) RETURNS boolean
AS '$libdir/pgxml_dom' LANGUAGE c STRICT;
I'm using GNU sed version 4.0.3.
I find the
On Fri, 22 Aug 2003 22:31:26 -0600
Robert Creager <[EMAIL PROTECTED]> said something like:
>
> I'm using GNU sed version 4.0.3.
>
Sorry, missed the rest:
GNU make 3.80
Mandrake Linux 9.1
PG 7.4Beta1
--
22:44:51 up 21 days, 15:26, 4 users, load average: 2.00, 2.03,
Hey,
Just wondering if the rule:
%.sql: %.sql.in
sed 's,MODULE_PATHNAME,$$libdir/$*g' $< >$@
is supposed to produce files like this:
CREATE OR REPLACE FUNCTION pgxml_parse(text) RETURNS boolean
AS '$libdir/pgxml_dom' LANGUAGE c STRICT;
I'm using:
GNU sed version 4.0.3.
GNU make 3
On Sat, 31 May 2003 00:11:26 -0400
Tom Lane <[EMAIL PROTECTED]> said something like:
>
> Cool ... but it's not immediately obvious which of these changes did the
> trick for you. What settings were you at before? And what's the
> details of the problem query?
>
> The first three settings you me
On Fri, 30 May 2003 09:11:39 -0400
Tom Lane <[EMAIL PROTECTED]> said something like:
>
> Also note that no amount of vacuuming will save you if the FSM is not
> large enough to keep track of all the free space. The default FSM
> settings, like all the other default settings in Postgres, are set
From: Tom Lane <[EMAIL PROTECTED]>
> The fix is in CVS.
Sure is. It works fine now. Thanks Tom.
Cheers,
Rob
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
23 matches
Mail list logo
