On 12/29/2011 09:19 AM, Merlin Moncure wrote:
I'll pass, thanks for all your help guys. It's been a blast.
I did not suggest that. I suggested they *might* be happening. In
lieu of a reproducible test case (a couple of us took a stab at
creating one ourselves and could not come up with
On Thu, Dec 29, 2011 at 10:20 AM, Greg Donald gdon...@gmail.com wrote:
On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane t...@sss.pgh.pa.us wrote:
SELECT pg_catalog.setval('cp_state_id_seq', 52, true);
SELECT pg_catalog.setval('cp_state_id_seq', 1, false);
These grep calls are showing just exactly
On 12/29/2011 08:13 AM, Greg Donald wrote:
On Wed, Dec 28, 2011 at 4:58 PM, Adrian Klaveradrian.kla...@gmail.com wrote:
What is the pg_dump command, with options, you are using?
My backup shell script contains:
/usr/bin/pg_dump cp | bzip2 $FILE
One possible issue that I see is the lack
On Wed, Dec 28, 2011 at 4:58 PM, Adrian Klaver adrian.kla...@gmail.com wrote:
What is the pg_dump command, with options, you are using?
My backup shell script contains:
/usr/bin/pg_dump cp | bzip2 $FILE
--
Greg Donald
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
On Thu, Dec 29, 2011 at 10:53 AM, Greg Donald gdon...@gmail.com wrote:
On Thu, Dec 29, 2011 at 10:27 AM, Merlin Moncure mmonc...@gmail.com wrote:
if you take a bzipped schema only dump (pg_dump -s), I'd be happy to
look it over and eliminate the 'operator error' class of issues that
Tom is
On Thu, Dec 29, 2011 at 10:27 AM, Merlin Moncure mmonc...@gmail.com wrote:
if you take a bzipped schema only dump (pg_dump -s), I'd be happy to
look it over and eliminate the 'operator error' class of issues that
Tom is thinking might be happening. private mail is ok.
Operator error? Wow..
On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane t...@sss.pgh.pa.us wrote:
These grep calls are showing just exactly not enough to prove
anything. I remain unclear as to what state is actually in the
database, or what is being dumped, but I suspect at this point that you
may have multiple sequences
On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane t...@sss.pgh.pa.us wrote:
SELECT pg_catalog.setval('cp_state_id_seq', 52, true);
SELECT pg_catalog.setval('cp_state_id_seq', 1, false);
These grep calls are showing just exactly not enough to prove
anything.
Those grep calls prove my old backups
On Tue, Dec 27, 2011 at 10:19 PM, Greg Donald gdon...@gmail.com wrote:
But then I have another table:
CREATE TABLE company (
id integer NOT NULL,
name character varying(64) NOT NULL,
[...]
);
The max(id) in that table is 33, but my sequence is NOT dumped correctly:
SELECT
Are you
sure that the sequence is being used to insert those values into the
table?
When I insert a new row into either of the tables I previously
described, the sequence 'Current value' increments by one. When I use
pg_dump to backup the database most of the setval() calls in my SQL
file
On Wednesday, December 28, 2011 6:54:54 am Greg Donald wrote:
Are you
sure that the sequence is being used to insert those values into the
table?
When I insert a new row into either of the tables I previously
described, the sequence 'Current value' increments by one. When I use
pg_dump
On Wed, Dec 28, 2011 at 9:07 AM, Adrian Klaver adrian.kla...@gmail.com wrote:
So how are the sequences being tied to the tables? In your previous post the
table definitions did not show a SERIAL type or a default of nextval().
The id columns were created using id serial NOT NULL.
I've gone
On Wednesday, December 28, 2011 7:18:01 am Greg Donald wrote:
On Wed, Dec 28, 2011 at 9:07 AM, Adrian Klaver adrian.kla...@gmail.com
wrote:
So how are the sequences being tied to the tables? In your previous post
the table definitions did not show a SERIAL type or a default of
nextval().
On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver adrian.kla...@gmail.com wrote:
Wonder if it is related to this:
http://archives.postgresql.org/pgsql-bugs/2011-11/msg00098.php
None of my sequences are named 'new'. What do you mean?
Might want to file bug report:
On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver adrian.kla...@gmail.com wrote:
Might want to file bug report:
http://www.postgresql.org/support/submitbug/
Can't, not at the moment anyway.
psql --version
psql (PostgreSQL) 9.1.1
I'm not running the latest 9.1.2 version as required by that
On Wednesday, December 28, 2011 7:51:24 am Greg Donald wrote:
On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver adrian.kla...@gmail.com
wrote:
Wonder if it is related to this:
http://archives.postgresql.org/pgsql-bugs/2011-11/msg00098.php
None of my sequences are named 'new'. What do you
On Wednesday, December 28, 2011 8:03:34 am Greg Donald wrote:
On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver adrian.kla...@gmail.com
wrote:
Might want to file bug report:
http://www.postgresql.org/support/submitbug/
Can't, not at the moment anyway.
psql --version
psql (PostgreSQL)
On Wed, Dec 28, 2011 at 10:20 AM, Adrian Klaver adrian.kla...@gmail.com wrote:
On Wednesday, December 28, 2011 7:51:24 am Greg Donald wrote:
On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver adrian.kla...@gmail.com
wrote:
Wonder if it is related to this:
On Wed, Dec 28, 2011 at 8:38 AM, Merlin Moncure mmonc...@gmail.com wrote:
On Wed, Dec 28, 2011 at 10:20 AM, Adrian Klaver adrian.kla...@gmail.com
wrote:
I was thinking of the more generic case. The problem with 'new' in the
above bug
is that it is a reserved word and the list of
On Wed, Dec 28, 2011 at 12:34 PM, Adrian Klaver adrian.kla...@gmail.com wrote:
On Wed, Dec 28, 2011 at 8:38 AM, Merlin Moncure mmonc...@gmail.com wrote:
On Wed, Dec 28, 2011 at 10:20 AM, Adrian Klaver adrian.kla...@gmail.com
wrote:
I was thinking of the more generic case. The problem with
Greg Donald gdon...@gmail.com writes:
Are you
sure that the sequence is being used to insert those values into the
table?
When I insert a new row into either of the tables I previously
described, the sequence 'Current value' increments by one.
According to what? If you look directly at a
Adrian Klaver adrian.kla...@gmail.com writes:
On Wednesday, December 28, 2011 7:51:24 am Greg Donald wrote:
None of my sequences are named 'new'. What do you mean?
I was thinking of the more generic case. The problem with 'new' in the above
bug
is that it is a reserved word and the list
On Wed, Dec 28, 2011 at 1:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Greg Donald gdon...@gmail.com writes:
Are you
sure that the sequence is being used to insert those values into the
table?
When I insert a new row into either of the tables I previously
described, the sequence 'Current
Greg Donald gdon...@gmail.com writes:
My pg_dump backups from before 9.1.1 were correct, now they are not:
diff backup_20111212031701.sql backup_20111223013539.sql | grep setval
| grep state_id
SELECT pg_catalog.setval('cp_state_id_seq', 52, true);
SELECT
On Wednesday, December 28, 2011 1:02:39 pm Greg Donald wrote:
On Wed, Dec 28, 2011 at 1:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Greg Donald gdon...@gmail.com writes:
Are you
sure that the sequence is being used to insert those values into the
table?
When I insert a new row into
I upgraded to PostgreSQL 9.1. I was using 8.4 previously.
My problem is with the new version of pg_dump. It no longer
(consistently) dumps my sequence values correctly.
For example, I have a table
CREATE TABLE setting (
id integer NOT NULL,
company_id integer NOT NULL,
[...]
);
26 matches
Mail list logo
