19.12.2012, 21:47, Tom Lane t...@sss.pgh.pa.us:
Kevin Grittner kgri...@mail.com writes:
Groshev Andrey wrote:
Mismatch of relation names: database database, old rel
public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel
public.plob.ВерсияВнешнегоДокумента$Документ
There is
On Thu, Dec 20, 2012 at 08:55:16AM +0400, Groshev Andrey wrote:
No, old database not use table plob..
only primary key
--
-- Name: plob.ВерсияВнешнегоДокумента$Документ; Type: CONSTRAINT; Schema:
public; Owner: postgres; Tablespace:
--
-- For binary upgrade, must preserve
20.12.2012, 13:00, Bruce Momjian br...@momjian.us:
On Thu, Dec 20, 2012 at 08:55:16AM +0400, Groshev Andrey wrote:
No, old database not use table plob..
only primary key
--
-- Name: plob.ВерсияВнешнегоДокумента$Документ; Type: CONSTRAINT; Schema:
public; Owner: postgres;
On Thu, Dec 20, 2012 at 03:19:17PM +0400, Groshev Andrey wrote:
20.12.2012, 13:00, Bruce Momjian br...@momjian.us:
On Thu, Dec 20, 2012 at 08:55:16AM +0400, Groshev Andrey wrote:
No, old database not use table plob..
only primary key
--
-- Name:
20.12.2012, 11:43, Bruce Momjian br...@momjian.us:
19.12.2012, 21:47, Tom Lane t...@sss.pgh.pa.us:
Kevin Grittner kgri...@mail.com writes:
Groshev Andrey wrote:
Mismatch of relation names: database database, old rel
public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel
On Thu, Dec 20, 2012 at 03:41:37PM +0400, Groshev Andrey wrote:
See that 786665369? That is the pg_class.oid of the plob in the old
cluster, and hopefully the new one. Find where the lob*_pkey index is
created and get that oid. Those should match the same names of the
pg_class.oid in
On Wed, Dec 19, 2012 at 10:19:30PM -0500, Bruce Momjian wrote:
On Wed, Dec 19, 2012 at 12:56:05PM -0500, Kevin Grittner wrote:
Groshev Andrey wrote:
Mismatch of relation names: database database, old rel
public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel
Bruce Momjian br...@momjian.us writes:
As you can see, ALTER INDEX renamed both the pg_constraint and pg_class
names. Is it possible someone manually updated the system table to
rename this primary key? That would cause this error message. The fix
is to just to make sure they match.
Does
On Thu, Dec 20, 2012 at 11:08:58AM -0500, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
As you can see, ALTER INDEX renamed both the pg_constraint and pg_class
names. Is it possible someone manually updated the system table to
rename this primary key? That would cause this error
Applied. We can mark this report closed. Groshev, let us know if you
have any further problems.
---
On Thu, Dec 20, 2012 at 07:19:48AM -0500, Bruce Momjian wrote:
On Wed, Dec 19, 2012 at 10:19:30PM -0500, Bruce Momjian
Can you post the full definition of the table on this public email list?
Also, why did the error think this was in the public schema? Any idea?
---
18.12.2012, 19:38, Bruce Momjian br...@momjian.us:
On Mon, Dec 17,
Groshev Andrey wrote:
Mismatch of relation names: database database, old rel
public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel
public.plob.ВерсияВнешнегоДокумента$Документ
There is a limit on identifiers of 63 *bytes* (not characters)
after which the name is truncated. In UTF8
Kevin Grittner kgri...@mail.com writes:
Groshev Andrey wrote:
 Mismatch of relation names: database database, old rel
public.lob.ÐеÑÑиÑÐнеÑнегоÐокÑменÑа$ÐокÑменÑ_pkey,
new rel
public.plob.ÐеÑÑиÑÐнеÑнегоÐокÑменÑа$ÐокÑменÑ
On Wed, Dec 19, 2012 at 01:51:08PM +0400, Groshev Andrey wrote:
Can you post the full definition of the table on this public email list?
Also, why did the error think this was in the public schema? Any idea?
---
On Wed, Dec 19, 2012 at 12:56:05PM -0500, Kevin Grittner wrote:
Groshev Andrey wrote:
Mismatch of relation names: database database, old rel
public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel
public.plob.ВерсияВнешнегоДокумента$Документ
There is a limit on identifiers of
On Wed, Dec 19, 2012 at 01:51:08PM +0400, Groshev Andrey wrote:
Can you post the full definition of the table on this public email list?
Also, why did the error think this was in the public schema? Any idea?
---
On Wed, Dec 19, 2012 at 10:35:11PM -0500, Bruce Momjian wrote:
There is another table ВерсияВнешнегоДокумента$Документ (without ^lob.)
It is referenced by a foreign key
(rlob.ВерсияВнешнегоДокумента$Документ-@Файл)
But as I understand it, the problem with the primary key.
Does the old
No, old database not use table plob..
only primary key
--
-- Name: plob.ВерсияВнешнегоДокумента$Документ; Type: CONSTRAINT; Schema:
public; Owner: postgres; Tablespace:
--
-- For binary upgrade, must preserve pg_class oids
SELECT
No, people can confuse writing, but it makes a computer.
Unfortunately, I have not found developer this database, but I understand the
logic was:
plob - primary key (lob ~ BLOB)
rlob - reference key (lob ~ BLOB)
Maybe if I describe the task, this part of the database, the problem is clear.
We
I'm initialize data dir with use ru_RU.UTF8, but this databse use CP1251, ie
one byte per character.
19.12.2012, 21:47, Tom Lane t...@sss.pgh.pa.us:
Kevin Grittner kgri...@mail.com writes:
Groshev Andrey wrote:
Mismatch of relation names: database database, old rel
On Tue, Dec 18, 2012 at 09:28:00AM +0400, Groshev Andrey wrote:
18.12.2012, 05:22, Bruce Momjian br...@momjian.us:
This is the first pg_upgrade mismatch report we have gotten about 9.1.
I have asked the reporter for details.
Is what is the full 9.1 version number?
On Mon, Dec 17, 2012 at 09:21:59PM -0500, Bruce Momjian wrote:
Mismatch of relation names: database database, old rel
public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel
public.plob.ВерсияВнешнегоДокумент
а$Документ
Failure, exiting
I am now confused over the error message
later in the log pg_dump, I found the definition of new rel
--
-- Name: plob.ВерсияВнешнегоДокумента$Документ; Type: CONSTRAINT; Schema:
public; Owner: postgres; Tablespace:
--
ALTER TABLE ONLY lob.ВерсияВнешнегоДокумента$Документ
ADD CONSTRAINT plob.ВерсияВнешнегоДокумента$Документ PRIMARY
On Tue, Dec 18, 2012 at 09:34:53PM +0400, Groshev Andrey wrote:
later in the log pg_dump, I found the definition of new rel
--
-- Name: plob.ВерсияВнешнегоДокумента$Документ; Type: CONSTRAINT; Schema:
public; Owner: postgres; Tablespace:
--
ALTER TABLE ONLY
This is the first pg_upgrade mismatch report we have gotten about 9.1.
I have asked the reporter for details.
Is what is the full 9.1 version number?
---
On Mon, Dec 17, 2012 at 03:33:40PM +0400, Groshev Andrey wrote:
18.12.2012, 05:22, Bruce Momjian br...@momjian.us:
This is the first pg_upgrade mismatch report we have gotten about 9.1.
I have asked the reporter for details.
Is what is the full 9.1 version number?
---
# rpm -qa
26 matches
Mail list logo
