acemeicn <[EMAIL PROTECTED]> writes:
> Here comes the problem. When a long SQL is excuted. I got
> the error as follow
> error:SQL Execute error 0 = Too much data was received.
The best guess I have is that this is a failure in Solaris' syslog.
There is certainly no such message anywhere in the
We need the output of EXPLAIN ANALYZE, from both versions if possible.
Also, pgsql-performance would be a better list for this...
On Tue, Oct 25, 2005 at 05:31:22PM -0600, Sidar L?pez Cruz wrote:
> what happend with postgresql 8.1b4 performance on query?
>
> look at this:
> select count(*) from
Hi everyone,
My name is Ken working in Tokyo,Japan. Please forgive my
poor English.
We have been using PostgreSQL7.3.4 on a Map GIS engine
since last year.To tune the system, I need to get the log
from PostgreSQL7.3.4 and analyze it.
Here comes the problem. When a long SQL is excuted. I got
the
what happend with postgresql 8.1b4 performance on query?
look at this:
select count(*) from fotos where archivo not in (select archivo from
archivos)
Aggregate (cost=4899037992.36..4899037992.37 rows=1 width=0)
-> Seq Scan on fotos (cost=22598.78..4899037338.07 rows=261716 width=0)
F
In article <[EMAIL PROTECTED]>,
Chris Browne <[EMAIL PROTECTED]> writes:
> A usual reason why I would want to dump everything except for a few
> tables is that those few tables are particularly enormous and
> particularly useless (at least, for the purposes of my dump).
> In that case, the LAST t
It's impossible to say without more information. What's the query that's
slow? What's EXPLAIN ANALYZE of that query show? How often are you
vacuuming? How often are you analyzing? What postgresql.conf options
have you changed from the defaults? What hardware is this running on?
The memory usage yo
Jeff Frost wrote:
> On Tue, 25 Oct 2005, Tom Lane wrote:
>
> >It's safe to exclude those, but those are hardly the only files that
> >might "disappear" in a live database. It'd be better to use a dump
> >tool that's less picky about the source data changing under it. We've
> >had similar reports
Jeff Frost wrote:
> Unfortunately, diffing the 8.0.4 docs against the 8.1 docs shows almost no
> useful differences. I was mostly hoping someone with knowledge of the WAL
> internal format could tell me how to extract the transactions from some and
> manually replay them in the db via psql wit
Hi All,
I am Kishore doing freelance development of J2EE applications.
We switched to use Postgresql recently because of the advantages it has over other commercial databases. All went well untill recently, untill we began working on an application that needs to maintain a huge database.
On Tue, 25 Oct 2005, Tom Lane wrote:
It's safe to exclude those, but those are hardly the only files that
might "disappear" in a live database. It'd be better to use a dump
tool that's less picky about the source data changing under it. We've
had similar reports about GNU tar being too smart f
Jeff Frost <[EMAIL PROTECTED]> writes:
> I noticed recently that my PITR base backups were occassionally returning
> non-zero, so I turned up the verbosity on rsync and it appears that
> occassionally a file vanishes out from under rsync while it's doing the base
> backup:
> ...
> Would it be ok
[EMAIL PROTECTED] writes:
> [EMAIL PROTECTED] wrote on 10/25/2005 02:31:51 AM:
>> It's possible with pg_restore to exclude that table on /restore/, but
>> that's not what you asked for..
>>
>> On 25.10.2005 11:08, Gourish Singbal wrote:
>> > pg_dump does not allow you to accomplish this task for su
On Mon, 24 Oct 2005, Bruno Wolff III wrote:
Please don't reply to existing threads to start new ones. That is probably why
your message didn't get any replies.
Point taken, but fortunately, Simon got back to me and essentially indicated
that I was out of luck.
On Mon, Oct 03, 2005 at 11:25
I noticed recently that my PITR base backups were occassionally returning
non-zero, so I turned up the verbosity on rsync and it appears that
occassionally a file vanishes out from under rsync while it's doing the base
backup:
700 4% 52.58kB/s0:00:00
16384 100%1.12M
[EMAIL PROTECTED] wrote on 10/25/2005
02:31:51 AM:
> It's possible with pg_restore to exclude that table on /restore/,
but
> that's not what you asked for..
>
> On 25.10.2005 11:08, Gourish Singbal wrote:
> > pg_dump does not allow you to accomplish this task for sure.
> >
> > On 10/20/05, Col
It's possible with pg_restore to exclude that table on /restore/, but
that's not what you asked for..
On 25.10.2005 11:08, Gourish Singbal wrote:
pg_dump does not allow you to accomplish this task for sure.
On 10/20/05, Colton A Smith <[EMAIL PROTECTED]> wrote:
I don't think this is possible
pg_dump does not allow you to accomplish this task for sure.
-- Best,Gourish Singbal
On 10/20/05, Colton A Smith <[EMAIL PROTECTED]> wrote:
Hi: I don't think this is possible, but I want to make sure. Let's say Ihave a database that I want to dump in its entirety, all except for one
particula
17 matches
Mail list logo