iption:
>
> cache lookup failed for relation 421062806
>
>
I am afraid you need to provide a lot more information for anyone to help
you. Postgres version you are using and the failing test case at the
minimum.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
t exist
>
>
You misspelled the database name. Please check.
vergunningen_sit - What you are connecting
vergunnigen_sit - What you created
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
r release ? I can not reproduce this
on the latest minor release of 9.2 branch.
There seem to be a fix which could be related to this:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f2366e584aea41b980f23fcf0a2e118efd7fb09b
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
te and half
before it got a shutdown request. So may be someone or some script is
actually stopping the service after a few minutes. I don't know
Windows much to guess who and why.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
--
Sent via pgsql-bu
or. I guess you must be running
a 32-bit machine because causing this error on a 64-bit machine will
take some serious over-setting for a number of parameters.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.o
o mentions:
"(Expressions of type date will be cast to timestamp and can therefore be
used as well.)"
ISTM that "for timestamp values only" means that a source of type interval
or time can not b used. Other functions will also accept those additional
types. I don't know if th
On Wed, Nov 7, 2012 at 4:51 PM, Saravanan Nagarajan wrote:
> Hi ,
>
> I am using "Copy From" while dumping bulk data into PGSQL DB from file.
> While I am trying to insert the rows, if the primary key already exists,
> the complete transaction terminated.
>
> Postgres cannot handle the constraint
On Fri, Sep 7, 2012 at 12:15 PM, Gezeala M. Bacuño II wrote:
> The instance is cloned solely for
> backup purposes with zero modifications and autovacuum disabled.
>
For your restricted use case, it might be worthwhile to
turn full_page_writes OFF before starting the server. That should
definit
On Fri, Sep 7, 2012 at 12:15 PM, Gezeala M. Bacuño II wrote:
>
> From pg_controldata right after starting the instance:
> Latest checkpoint location: 4441/5E681F38
> Prior checkpoint location:4441/5E67D140
> Latest checkpoint's REDO location:4441/5E681F38
> Latest checkp
On Fri, Sep 7, 2012 at 2:43 AM, Alvaro Herrera wrote:
> Excerpts from Boy de Laat's message of jue sep 06 17:24:35 -0300 2012:
> >
> > At the time my backup starts i see much WAL logs being generated?
>
> I guess we'd need to see what the generated WAL logs are, either with
> xlogdump or XLOG_DEBU
On Thu, Dec 11, 2008 at 2:05 PM, Pavan Deolasee
<[EMAIL PROTECTED]> wrote:
>
> Isn't the shared memory on Linux non-swappable, unlike Solaris where
> you have an option to make is swappable ?
Or may be my linux kernel knowledge is stale. I see a SHM_LOCK/UNLOCK
operations in
t. I
don't know if these pages are counted as part of the OS cache, but
assuming they are, I don't see any problem with the above observation.
May be you can try to write a C program which creates, attaches and
accesses every page of the shared memory and check if you see the same
be
weather http or ftp. Is any way to get
> this
> particular version of PostgreSQL?
>
>
See if this helps, though I have no idea why this is not shown in the
listing.
http://www.postgresql.org/ftp/binary/v8.2.4/win32/
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
n with OID 16390 does not exist
CONTEXT: SQL statement "INSERT INTO test VALUES (1)"
PL/pgSQL function "testfunc" line 2 at SQL statement
If upgrading to 8.3.1 is an option, you can try that.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
-
Sent via pg
loc request size 4294967280
>
>
Hopefully this is already fixed.
http://archives.postgresql.org/pgsql-committers/2008-02/msg00101.php
The symptoms look the same. Dropping the tables would have deleted several
rows in the pg_class table and subsequent vacuuming of the table may trigger
t
15 matches
Mail list logo