Dear colleagues,
For the last few hours I tried to implement $subj, to no avail. I tried to use
create rule (no grant statement allowed), create function (syntax error on $1),
etc.
I have roles mng and rdr, and want that any newly created class (table, view,
seq, index) will be available for
I'm getting this loading some large (1 million row) tables. Is this
anything to be concerned about?
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
> Are you sure that the destination database has the same encoding
> declaration as the source did?
That's what I'd be looking at - I had similar problems a few weeks ago. See
this thread:
http://archives.postgresql.org/pgsql-admin/2007-12/msg00235.php
THINK BEFORE YOU PRINT - Save paper if you
> > Are you sure that the destination database has the same encoding
> > declaration as the source did?
>
> That's what I'd be looking at - I had similar problems a few weeks ago.
> See
> this thread:
> http://archives.postgresql.org/pgsql-admin/2007-12/msg00235.php
I've been thinking about this,
> "Phillip Smith" <[EMAIL PROTECTED]> writes:
> > I've been thinking about this, and while I don't agree it's a bug, I
> think
> > that perhaps PostgreSQL should raise a notice or warning that the
> > destination database has different encoding than the file being
> restored...?
>
> If Postgres ac
"Phillip Smith" <[EMAIL PROTECTED]> writes:
> I've been thinking about this, and while I don't agree it's a bug, I think
> that perhaps PostgreSQL should raise a notice or warning that the
> destination database has different encoding than the file being restored...?
If Postgres actually *knows* t
Dean Gibson (DB Administrator) wrote:
> I'm getting this loading some large (1 million row) tables. Is this
> anything to be concerned about?
No, it's normal. It means the autovacuum task was cancelled in order to
avoid blocking your regular Postgres sessions.
If it's only during table loadin
"Phillip Smith" <[EMAIL PROTECTED]> writes:
> How has the software been misinformed and how can we avoid it then? :)
Well, if that were entirely clear then we could fix it.
> The start of the pgdump sets the client encoding, so shouldn't that tell PG
> that things could get strange?
The problems
