Re: Apparent Problem With NULL in Restoring pg_dump

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Apparent Problem With NULL in Restoring pg_dump
Date: 2011-09-16 22:14:50
Message-ID: alpine.LNX.2.00.1109161511030.26931@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 15 Sep 2011, Andy Colson wrote:

> Trim it up:
> andy=# select '['|| rtrim(trim(trailing E'\n' from a)) || ']' from junk;

Andy,

Scrolling through the table with rows ordered by date and chemical I find
no duplicates ... so far. However, what I do find is that the above did not
work:

GW-22 | 1998-12-16 | Zinc | 0.01
GW-22 | 1998-12-16 | pH | 7.83
GW-22 +| 1999-03-09 | Alkalinity, Bicarbonate | 97
| | |
GW-22 +| 1999-03-09 | Alkalinity, Total | 80
| | |
GW-22 +| 1999-03-09 | Aluminum | 0.01
| | |
GW-22 +| 1999-03-09 | Antimony |

As my previous message noted, selecting rows with two spaces before the
newline returned 0 rows.

I'll continue looking for duplicates, but I suspect there are none. I just
need to get rid of the newlines, drop all rows for site_id from the
chemistry table, then insert the cleaned rows from the junk table.

Regards,

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edson Carlos Ericksson Richter 2011-09-16 22:39:56 Foreign PostgreSQL server
Previous Message Merlin Moncure 2011-09-16 21:48:47 Re: Indexes not allowed on (read-only) views: Why?