| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | antsumees(at)hot(dot)ee |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: need help |
| Date: | 2006-04-21 21:49:14 |
| Message-ID: | 14072.1145656154@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
<antsumees(at)hot(dot)ee> writes:
> pg_dump: server version: 8.1.3; pg_dump version: 8.1.0
> pg_dump: proceeding despite version mismatch
> pg_dump: DEBUG: StartTransactionCommand
> pg_dump: DEBUG: StartTransaction
> pg_dump: DEBUG: name: unnamed; blockState: DEFAULT; state: =
> INPROGR, xid/subid/cid: 475771/1/0, nestlvl: 1, children: <>
> what means here unnamed: blockState is it somekind of big problem or =
> not?
It means you've got logging turned up to an unreasonably high level ;-)
There is little point in enabling debug messages if you're not a backend
hacker.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amadeus Zilfinski | 2006-04-22 19:58:17 | Using PostgresQL as a database back-end |
| Previous Message | Richard Broersma Jr | 2006-04-21 21:13:36 | Re: Oracle Analytic Functions for PostreSQL |