On Friday January 19 2007 2:11 am, Csaba Nagy wrote:
>
> > I afraid I don't see how any of the answers I saw discussed
> > fit a 24x7 operation. Reindex, drop index, vacuum full, ...
> > they all block production queries of one sort or another for
> > significant periods of time (minutes) on large
We have a large number (50+) of pre-8.2 clusters. How can I
best/most easily identify those indices most bloated and in need
of reindex/rebuilding?
Ed
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://ar
From the FAQ:
1.14) Will PostgreSQL handle recent daylight saving time changes
in various countries?
PostgreSQL versions prior to 8.0 use the operating system's
timezone database for daylight saving information. All current
versions of PostgreSQL 8.0 and later contain up-
How do I fix this 7.4.6 issue short of initdb?
invalid page header in block 110 of relation "pg_statistic"
I looked at the block via pg_filedump (included below), and it
does not appear to me to be corrupted, so not sure what I would
zero out, if anything.
TIA.
Ed
***
On Wednesday February 7 2007 9:01 am, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > How do I fix this 7.4.6 issue short of initdb?
> > invalid page header in block 110 of relation "pg_statistic"
> > I looked at the block via pg_filedu
I've been periodically collecting the stats stored in
pg_statio_all_tables and pg_stat_database for ~30 different
clusters, and have noticed a curiosity.
I would have thought that for a given period, the change in
pg_stat_database.blks_read would be <= the sum of the changes in
pg_statio_user
Oops, typo: I reversed the inequality. I've corrected it below.
On Friday February 23 2007 2:02 pm, Ed L. wrote:
> I've been periodically collecting the stats stored in
> pg_statio_all_tables and pg_stat_database for ~30 different
> clusters, and have noticed a curiosit
On Friday February 23 2007 3:06 pm, Ed L. wrote:
> > I've been periodically collecting the stats stored in
> > pg_statio_all_tables and pg_stat_database for ~30 different
> > clusters, and have noticed a curiosity... The table-level IO stats
> > appear to be typi
I am seeing the following error in pgsql 8.1.2:
2007-03-05 10:00:51.106 PST [9834]DEBUG: vacuuming "pg_toast.pg_toast_1260"
2007-03-05 10:00:51.106 PST [9834]DEBUG: index "pg_toast_1260_index" now
contains 0 row versions in 1 pages
2007-03-05 10:00:51.106 PST [9834]DETAIL: 0 index
On Tuesday March 6 2007 12:20 pm, Peter Eisentraut wrote:
> Ed L. wrote:
> > I am seeing the following error in pgsql 8.1.2:
> >
> > ERROR: could not access status of transaction 3229475082
> > DETAIL: could not open file "pg_clog/0C07": No such file or
&g
On Tuesday March 6 2007 3:53 pm, Joshua D. Drake wrote:
>
> > Is restarting with 8.1.8 a known solution for this problem?
> > Or is an initdb required to fix it?
>
> You can update to 8.1.8 (if you are running 8.1.x) without an
> initdb.
Right. I'm asking if the fix for this problem is in the n
On Tuesday March 6 2007 11:52 pm, Peter Eisentraut wrote:
> Ed L. wrote:
> > Right. I'm asking if the fix for this problem is in the new
> > 8.1.8 software, or in the new DB structure resulting from
> > the initdb, or perhaps both.
>
> There is no new DB structur
On Wednesday February 7 2007 9:01 am, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > How do I fix this 7.4.6 issue short of initdb?
> > invalid page header in block 110 of relation "pg_statistic"
> > I looked at the block via pg_filedu
On Wednesday March 7 2007 3:13 am, Martijn van Oosterhout wrote:
> On Wed, Mar 07, 2007 at 02:29:08AM -0700, Ed L. wrote:
> > Perhaps my question was not clear enough. Let me rephrase:
> > Does the fix for this problem comes from a *fresh* DB
> > structure resulting from
We have a 7.4.6 cluster which has been running on an HP B.11.00
box for quite sometime. The IT group applied daylight savings
patches to the OS, but the cluster is still showing the
incorrect timezone:
$ psql -c "select now()"
now
---
2
On Monday March 12 2007 1:07 pm, Ed L. wrote:
> Does this mean that we need to restart these clusters in order
> to get the timezone updates from the OS? Are they cached in
> the postmaster?
Nevermind. I just found it via googling.
Would I be correct in understanding that every pre-8.
On Monday March 12 2007 4:08 pm, Martijn van Oosterhout wrote:
> On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
> > Would I be correct in understanding that every pre-8.0
> > cluster must be restarted in order for the OS changes to
> > take affect?!?
>
>
This is pgsql 8.2.3:
% psql -c "drop role mygroup"
ERROR: role "mygroup" cannot be dropped because some objects
depend on it
DETAIL: 227 objects in this database
How do I identify what these dependent objects are?
I've removed all of the users from this group, turned up server
logging to deb
On Wednesday April 4 2007 4:35 pm, Alvaro Herrera wrote:
>
> Note that you can give the objects owned by that role to
> someone else with REASSIGN OWNED, and drop the objects with
> DROP OWNED (note that they act differently regarding grants;
> see the docs)
Yes, but how do identify what they are
On Wednesday April 4 2007 4:39 pm, Ed L. wrote:
> On Wednesday April 4 2007 4:35 pm, Alvaro Herrera wrote:
> > Note that you can give the objects owned by that role to
> > someone else with REASSIGN OWNED, and drop the objects with
> > DROP OWNED (note that they act differe
On Wednesday April 4 2007 4:41 pm, Ed L. wrote:
> On Wednesday April 4 2007 4:39 pm, Ed L. wrote:
> > On Wednesday April 4 2007 4:35 pm, Alvaro Herrera wrote:
> > > Note that you can give the objects owned by that role to
> > > someone else with REASSIGN OWNED, and drop
On Wednesday April 4 2007 4:48 pm, Alvaro Herrera wrote:
> > Yes, but how do identify what they are so that I know if I
> > want to DROP OWNED them?
>
> There's no way AFAICT, short of peeking the catalogs (or
> information_schema). Try pg_shdepend.
I guess if the bug were fixed, it'd be a non-is
On Wednesday April 4 2007 5:02 pm, Alvaro Herrera wrote:
> > I guess if the bug were fixed, it'd be a non-issue.
>
> Sure, please submit a patch. It should not be too difficult.
Perhaps this could be added to the TODO list? I won't get to it
anytime soon.
Ed
---(end o
On Wednesday April 4 2007 5:37 pm, Bruce Momjian wrote:
> > Perhaps this could be added to the TODO list? I won't get
> > to it anytime soon.
>
> Yes. What should the TODO text be?
See if the attached patch is acceptable. If not, perhaps the
TODO text should be:
Enable end user to identify de
After a reboot (and usually after an OS patch) on our HP-UX 11.23
64-bit Itanium DB servers, our libpq/DBD::Pg libraries cease to
work. Instead, they give the standard message you get when the
DB cluster is not running. But we *know* it is running and all
access paths are working. We have f
On Thursday 26 April 2007 8:50 am, Ed L. wrote:
> After a reboot (and usually after an OS patch) on our HP-UX
> 11.23 64-bit Itanium DB servers, our libpq/DBD::Pg libraries
> cease to work. Instead, they give the standard message you
> get when the DB cluster is not running. But we
On Thursday 26 April 2007 9:42 am, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > After a reboot (and usually after an OS patch) on our HP-UX
> > 11.23 64-bit Itanium DB servers, our libpq/DBD::Pg libraries
> > cease to work. Instead, they give the
On Tuesday 01 May 2007 2:23 pm, Tom Lane wrote:
> Well, it's going wrong here:
>
> socket(AF_INET, SOCK_STREAM, 0) .. = 4
> setsockopt(4, 0x6, TCP_NODELAY, 0x9fffe210, 4) ... = 0
> fcntl(4, F_SETFL, 65536) . = 0
> fcntl(4, F_SETFD, 1)
On Tuesday 01 May 2007 2:46 pm, Ed L. wrote:
> It is indeed a local connection using PGHOST=`hostname`. That
> name maps to one of the external NIC IPs, not to the normal
> 127.0.0.1 loopback address. For context, I've seen this a
> number of times over the past couple years,
I *think* I'm seeing "vacuum analyze" queries launched automatically on an
8.0.0beta3 (unless I have a rogue autovac running that I haven't spotted).
Is this something new in 8.0 and to be expected?
My settings:
#vacuum_cost_delay = 0# 0-1000 milliseconds
#vacuum_cost_page_hit = 1
On Monday October 18 2004 2:39, Jan Wieck wrote:
> On 10/18/2004 12:49 AM, Ed L. wrote:
> > I *think* I'm seeing "vacuum analyze" queries launched automatically on
> > an 8.0.0beta3 (unless I have a rogue autovac running that I haven't
> > spotted). Is thi
I have 5 corrupted page headers as evidenced by these errors:
ERROR: Invalid page header in block 13947 of ...
The corruption is causing numerous queries to abort. First option is to try
to salvage data before attempt restore from backup. I want to try to edit
the file to zero out t
On Wednesday October 20 2004 5:34, Ed L. wrote:
> I have 5 corrupted page headers as evidenced by these errors:
>
> ERROR: Invalid page header in block 13947 of ...
>
> The corruption is causing numerous queries to abort. First option is to
> try to salvage data before at
On Wednesday October 20 2004 10:12, Ed L. wrote:
> On Wednesday October 20 2004 10:00, Tom Lane wrote:
> > "Ed L." <[EMAIL PROTECTED]> writes:
> > > In other words, how do I calculate which bytes to zero to simulate
> > > zero_damaged_pages??
> >
On Wednesday October 20 2004 10:00, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > In other words, how do I calculate which bytes to zero to simulate
> > zero_damaged_pages??
>
> Why simulate it, when you can just turn it on? But anyway, the ans
On Wednesday October 20 2004 10:43, Ed L. wrote:
> On Wednesday October 20 2004 10:12, Ed L. wrote:
> > On Wednesday October 20 2004 10:00, Tom Lane wrote:
> > > "Ed L." <[EMAIL PROTECTED]> writes:
> > > > In other words, how
On Thursday October 21 2004 10:07, Tom Lane wrote:
> "Henry Combrinck" <[EMAIL PROTECTED]> writes:
> > I've been approached by the development people about removing the
> > 'public' schema. They complain about having to manually remove the
> > 'public_' tag from table names generated by their deve
Wow. First, thanks again for all your efforts, Jan. Second, I'm
disappointed to hear the slony author and lead developer is leaving the
slony leadership. When is that going to happen? And what does that mean
with respect to your future involvement in slony?
Ed
On Friday October 22 2004 7:
I've installed both 32-bit and 64-bit executables of 7.4.5 on ia64 running
HP-UX B.11.23. The 32-bit version works fine and accepts both local and
remote connections. The 64-bit version, however, rejects any/all attempts
to connect with the following message:
FATAL: no pg_hba.conf entry for
On Friday October 22 2004 5:11, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I've installed both 32-bit and 64-bit executables of 7.4.5 on ia64
> > running HP-UX B.11.23. The 32-bit version works fine and accepts both
> > local and remote
On 7.4.6, is there any problem with defining one column of a view to be a
string literal? For example ...
$ psql -c "create view fooview as select 'bar' as footype"
WARNING: column "footype" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
CREATE VIEW
Or is this warning j
On Wednesday October 27 2004 5:24, Tom Lane wrote:
> An example of what you won't be able to do:
>
> regression=# select distinct * from fooview;
> ERROR: failed to find conversion function from "unknown" to text
Is that 8.0 you're working against there? Here's my 7.4.6 installation:
$ psql -c
On Wednesday October 27 2004 5:34, Ed L. wrote:
> On Wednesday October 27 2004 5:24, Tom Lane wrote:
> > An example of what you won't be able to do:
> >
> > regression=# select distinct * from fooview;
> > ERROR: failed to find conversion function from "un
On Thursday October 28 2004 11:42, Robby Russell wrote:
>
> Thanks, this seems to work well. My goal is to actually create a php
> function that takes a result and returns the insert_id like
> mysql_insert_id() does, but without needing to know the sequence names
> and such. I would make a psql fun
On Thursday October 28 2004 5:31, Michael Fuhr wrote:
> On Thu, Oct 28, 2004 at 04:51:05PM -0600, Ed L. wrote:
> > But I didn't understand why you care to get rid of the explicit
> > reference to the sequence object in your code in the first place. In
> > PostgreSQL, at
What does this mean?
WARNING: Rel pg_class: TID 17/13: InsertTransactionInProgress 106004881 -
can't shrink relation
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
I asked this on the slony list, but maybe more appropriate to ask here...
I'm using slony to replicate a database with 200 sequences. To replicate
these with slony or our modified dbmirror, the replicator polls every
sequence relation (select last_value...) on each syncronization interval.
Th
On Sunday October 31 2004 8:25, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > Are triggers on sequences a reasonable feature request/hope for Pgsql?
>
> I don't think so. Since sequences are inherently not transactional,
> it seems wrong to
What is the conventional wisdom about routine reindexing with 7.4.6 and 8.0?
Is it still considered an important maintenance task? If so, how
frequently is it needed?
Ed
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
While dealing with filesystem bloat issues, I found a large file
named 43710738, recently updated and sitting in one of my
database directories,
$ ls -lh ../../../data/base/11259315/43710738
-rw---1 dba dba 1016M Nov 3 17:05
../../../data/base/11259315/43710738
... with no
I have a few high-volume, fairly large clusters that I'm struggling to keep
up 24x7x365. I want to ask for advice from anyone with similar experience
or hard-won wisdom.
Generally these are clusters with 100-200 queries/second, maybe 10GB-30GB of
data (always increasing), and maybe 10% writ
On Saturday November 6 2004 7:34, Net Virtual Mailing Lists wrote:
> Is there a way to create an index that would make this query be efficient
> and not perform a sequential scan?
>
> SELECT count(*) AS count,id FROM sometable GROUP BY id;
>
> .. I've considered creating a rule on this table which
I'd like to have a DB client connect using a username ('psuedodba')
different from the creator/owner ('dba') of the DB and its tables, but
still have that username be able to do everything the creator/owner can do
(alter tables, drop databases, etc). It appears that
"createuser -d -a
On Saturday November 6 2004 12:04, Randy Yates wrote:
> At the risk of asking an ill-formed oft-asked question that's
> probably in the FAQ, is there any report generation tools that
> are particularly suited for use with postgres databases?
Not sure if you're looking for open source products or c
On Saturday November 6 2004 2:13, Franco Bruno Borghesi wrote:
> the simplest way to do it seems to be adding a SERIAL column to your
> table, and then adding a primary key constraint:
>
> 1)insert data into table
> 2)ALTER TABLE ADD id SERIAL;
> 3)ALTER TABLE ADD CONSTRAINT _pk PRIMARY KEY (id);
A power failure led to failed postmaster restart using 7.4.6 (see output
below). The short-term fix is usually to delete the pid file and restart.
I often wonder why ipcs never seems to show the shared memory
block in question? Am I using the wrong command? Does the key
mentioned by pgsql map
On Monday November 8 2004 6:16, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > A power failure led to failed postmaster restart using 7.4.6 (see
> > output below). The short-term fix is usually to delete the pid file
> > and restart.
> >
>
On Monday November 8 2004 7:24, Ed L. wrote:
> On Monday November 8 2004 6:16, Tom Lane wrote:
> > "Ed L." <[EMAIL PROTECTED]> writes:
> > > A power failure led to failed postmaster restart using 7.4.6 (see
> > > output below). The short-term fix
On Monday November 8 2004 8:41, Tom Lane wrote:
>
> BTW, do you know what all those shmem segments are for? My Linux box
> shows only one segment in use besides the ones Postgres is using.
Looks like Ximian Evolution apps, X, Mozilla, Wombat, etc ...
Ed
---(end of broad
I'm wrestling with tracking down a deadlock. Here's a 7.4.6 deadlock
message:
ERROR: deadlock detected
DETAIL: Process 15655 waits for ShareLock on transaction 9381; blocked by
process 15600.
Process 15600 waits for ShareLock on transaction 9388; blocked by process
15655.
I know the origin
On Tuesday November 9 2004 2:16, Oliver Elphick wrote:
> On Mon, 2004-11-08 at 17:47 -0700, Ed L. wrote:
> > I often wonder why ipcs never seems to show the shared memory
> > block in question?
>
> The permissions of the shared memory block and the semaphore arrays are
>
On Tuesday November 9 2004 10:36, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I know the original statement is printed right after this, but with
> > complex triggers doing lots of write queries, I'm finding it difficult
> > to identify which
On Tuesday November 9 2004 1:37, Tom Lane wrote:
> >> The shared memory block would certainly not still exist after a system
> >> reboot, so what we have here is a misleading error message. Looking
> >> at the code, the most plausible explanation appears to be that
> >> shmctl(IPC_STAT) is failing
On Tuesday November 9 2004 4:35, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I noticed that ipcs on my linux box has a command-line option to list
> > the pid that created the segment. Not sure if such a library exists in
> > usable form, but loo
On 7.4.6 and earlier, we use apache's log rotation program as follows:
pg_ctl start | rotatelogs ...
If we have a configuration failure, say a bad parameter in postgresql.conf,
we often don't quickly notice because it goes to stdout (into the log).
It'd be nice if it went to stderr a
Is there a SQL query to retrieve the start time of a) when the postmaster
was started, and/or b) when the stats were last reset? I'd like to
calculate a few rates over time...
TIA.
Ed
---(end of broadcast)---
TIP 3: if posting/reading through
I have "big_table" (1M rows) and "small_table" (1K rows) with
identical schemas and together in a view as follows:
create view big_view as
select *, 'big_table'::varchar as source from big_table
union
select *, 'small_table'::varchar as sou
I need to reclaim the diskspace from a heavily updated 7.3.4 table which has
grown 95% bloated to 20gb of disk (indices and toast included), and I need
to reclaim it while the table continues to get updates, and without
interrupting/delaying access more than a few seconds. This is an
explanat
On Friday December 3 2004 1:54, Martijn van Oosterhout wrote:
>
> For this, check the FSM settings. It can only keep track of a limited
> number of pages. So if your tuples are large it may not be able to
> track it all...
>
> The FSM should be set big enough to cover all the space that might be
>
On Friday December 3 2004 9:09, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > [SIDEBAR: Vacuum + fsm is not working as
> > I expected; it is clearly not reclaiming space resulting from the
> > UPDATEs. If I UPDATE 1 rows and then run vacu
On Saturday December 4 2004 1:01, Ed L. wrote:
>
> ...I have a
> shell game using rules that goes like this for bloated table foo:
> ...
> begin
> drop view foo
> alter table slim_foo rename to foo
> commit
>
> Some basic testing for my particulars sugge
On Tuesday December 7 2004 5:58, marcelo Cortez wrote:
> >
> > > /psql someDatabase
> > > vaccum full verbose;
> > > but nothing informs.
> > > in which cases vacuum do not inform anything?
> > > postgresql 7.4 on red hat 9.0
> > > any clue be appreciate.
> > > best regards
> >
> > Is your server
On Tuesday December 7 2004 6:27, Ed L. wrote:
> On Tuesday December 7 2004 5:58, marcelo Cortez wrote:
> > > > /psql someDatabase
> > > > vaccum full verbose;
> > > > but nothing informs.
> > > > in which cases vacuum do not inform anything?
>
Is the error below a bug? Or a feature?
% cat foo.sql
SELECT version();
CREATE TABLE foo ( "key" serial NOT NULL PRIMARY KEY, msg character(100));
CREATE TABLE bar ( "key" serial NOT NULL PRIMARY KEY, msg character(100));
CREATE VIEW baz AS SELECT * FROM foo UNION ALL SELECT * FROM bar;
CREATE
I need to convert an existing unique index on a very heavily inserted table
into a primary key. Alter table works, but locks the table for too long.
As a hack, can I just set pg_index.indisprimary = 't' and
pg_constraint.contype = 'p' for the appropriate row in each? This is for
7.4.6 and 8
I'm getting the following warning on 8.0beta3:
WARNING: group with ID 103 does not exist
It is true that I don't have a pg_group.grosysid = 103,
but I don't understand why the backend expects it in the
first place. Here's an example:
% psql -c "create user \"[EMAIL PROTECTED]""
CREATE
Is it possible to tell if a column in a NEW record in a plpgsql function was
explicitly specified as NULL or simply left out altogether?
For example, if I have the following table:
create table foo(id serial, msg varchar)
Is it possible to distinguish within plpgsql between these two q
On Tuesday January 11 2005 8:40, Tom Lane wrote:
> >
> > Is it possible to distinguish within plpgsql between these two queries?
> >
> > insert into foo (msg) values ('Hello')
> > insert into foo (id, msg) values (NULL, 'Hello')
>
> Well, yes, because the default value in the former case wi
On Tuesday January 11 2005 8:58, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > The reason I ask is because I'd like to allow any explicitly specified
> > values for the view insert, including NULL, to be passed through to the
> > tab
I'm looking at some 7.3.4 vacuum output, and at first glance it does not
appear that vacuum is reclaiming any dead tuple space if there is even a
single open transaction, even if the open transaction does not in any way
reference the table being vacuumed. Is that correct? Is the behavior
dif
On Wednesday January 12 2005 11:10, Scott Marlowe wrote:
>
> I believe the problem is occurring if the open transaction is older than
> the tuples that could be vacuumed. The MVCC system means that as long
> as a transaction that started X hours ago is still open, the tuples that
> have been freed
On Wednesday January 12 2005 1:08, Clodoaldo Pinto wrote:
> There was a power failure and then the postgresql service didn't start on
> system restart:
>
> The last activity before power failure was a vacuum full and after that
> nothing at all for more than one hour.
> Is there anyway to know why
On Wednesday January 12 2005 11:30, Michael Fuhr wrote:
> On Wed, Jan 12, 2005 at 11:49:12AM -0700, Ed L. wrote:
> > Is it possible via SQL query to tell how long a transaction has been
> > open?
>
> I'm not aware of a way to find out when a transaction
On Thursday January 13 2005 5:50, Alvaro Herrera wrote:
> On Wed, Jan 12, 2005 at 11:30:50PM -0700, Michael Fuhr wrote:
> > On Wed, Jan 12, 2005 at 11:49:12AM -0700, Ed L. wrote:
> > > Is it possible via SQL query to tell how long a transaction has been
> > > open?
>
On Thursday January 13 2005 10:09, Michael Fuhr wrote:
>
> For idle transactions pg_stat_activity shows " in transaction"
> and the query_start column shows when the transaction became idle
> (i.e., when the last statement completed). So if long-lived idle
> transactions are the problem, then at l
On Thursday January 13 2005 11:37, Michael Fuhr wrote:
>
> That'll show which transaction is oldest but not how long it's been
> open or idle, i.e., whether it's "long-open" or not. I assumed,
> perhaps incorrectly, that he was already looking at pg_locks and
> wanted to find out which of those tr
There's probably an obvious answer for this, but I couldn't see it in the
docs. What's the simplest way to concatenate multiple same-column values
in SQL?
For example, suppose I have table foo (key integer, id integer, entry
varchar) with data
key id entry
1 1
I am seeing a minor error and curious to learn if it is user error
or a bug.
I have a function (using 8.1devel) that returns a set of rows listing
the sizes of the various components of a relation (indices, toast, etc).
Here's an example of a successful call:
select *
from relation_size_compon
I'm trying to optimize a large query by looking at
EXPLAIN ANALYZE output. Here's what I think may be
the most relevant snippet:
21 -> Nested Loop (cost=0.00..108.85 rows=1 width=1196) (actual
time=4769.59..4769.59 rows=0 loops=1)
22 -> Nested Loop (cost=0.00..64.78 rows=4 wi
On Wednesday February 9 2005 11:29, Roy Souther wrote:
> I cannot find any information about wether PostgreSQL has
> EXTPROC or not. Can someone tell me if it dose or if there is
> a better way to do this.
Not sure what version you're using, but sounds like a job for
perl (plperl) + a select rule
On Wednesday February 9 2005 12:56, Alvaro Herrera wrote:
> On Wed, Feb 09, 2005 at 12:54:27PM -0700, Ed L. wrote:
> > sped up the query to sub-second. This is a 7.3.4 cluster.
> > I wonder if this that 7.3 index bloat bug?
>
> Hard to say, because you didn't provide m
On Wednesday February 9 2005 2:21, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> >
> > 21 -> Nested Loop (cost=0.00..108.85 rows=1
> > width=1196) (actual time=4769.59..4769.59 rows=0 loops=1) 22
> > -> Nested Loop (cost=0.
On Wednesday February 9 2005 3:13, Martijn van Oosterhout wrote:
>
> In general, the EXPLAIN ANALYZE output follows the planner
> output as close as possible. If you look at the original query
> posted, it showed an Index Scan costing 4.63..4.63 which means
> the index scan is taking (on average) 4
Thinking about how to make this analysis faster and less labor-
intensive ...
I know of no other way to get the detailed performance data provided
via EXPLAIN ANALYZE without just painfully disassembling a query.
It seems it would be pretty useful w/r/t performance monitoring to
be able to ret
On Wednesday February 9 2005 7:31, David Fetter wrote:
> On Wed, Feb 09, 2005 at 04:34:30PM -0700, Ed L. wrote:
> > Thinking about how to make this analysis faster and less
> > labor- intensive ...
> >
> >SELECT node_id, op, parent_node_id, index, relation,
> >
On Wednesday February 9 2005 8:07, Ed L. wrote:
> >
> > Well, I'm a little bored; I've got tomorrow off, and this
> > seems like it might be doable in the kind of high-level
> > PL/Foo's with which I'm familiar. What would the returning
> > ro
On Wednesday February 9 2005 10:10, Michael Fuhr wrote:
>
> > (And no, EXECUTE doesn't help.) This seems like an
> > oversight. We already have some understanding in the
> > backend that certain utility commands return query results;
> > the SPI code should be letting those results be scanned as
On Thursday February 10 2005 5:01, David Fetter wrote:
> On Thu, Feb 10, 2005 at 05:19:41PM -0500, Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> > > I'd be delighted to, but I'm not sure how to see to it
> > > that EXPLAIN gets the CMD_SELECT flag. What all files
> > > need to cha
I'm seeing some unpleasant database cluster seizures. After
running fine for hours, days, even weeks, all of a sudden new
connections via psql, DBI, libpq, all completely hang with no
log message or error, while existing connections can continue to
execute queries, log messages, etc. Postmas
On Wednesday February 16 2005 7:48, David Fetter wrote:
> On Wed, Feb 16, 2005 at 04:46:09PM +0530, Nageshwar Rao wrote:
> > Is there is way to load data from as Microsoft excel into
> > database tables in postgresql7.4.x
>
> Once you've upgraded to 8.0x--a good idea anyhow--you can use
> DBI-Link
101 - 200 of 281 matches
Mail list logo
