Some time ago we upgraded from v. 8.4.4 to 9.4.0 and we are seeing errors in
some regression tests.
LOCATION: exec_simple_query, postgres.c:887
ERROR: 40001: could not serialize access due to read/write dependencies among
transactions
Detail can be one of these:
DETAIL: Reason code: Cance
Hi,
One of our sites ran into a problem with database installation:
initdb failed
FATAL: unexpected data beyond EOF in block 19 of relation base/1/2609
HINT: This has been seen to occur with buggy kernels; consider updating your
system.
STATEMENT: COMMENT ON FUNCTION euc_jis_2004_to_shift_jis_20
Here is what you should do:
1. Build Postgres with --prefix set to some empty directory.
2. Run install.
3. Bundle up the resulting install tree as part of your tarball. Do not
editorialize upon the relative locations of its contents.
4. Drop the install tree wherever you want on the target machi
On Fri, Dec 10, 2010 at 10:54 AM, Andrew Dunstan wrote:
> Here's my understanding.
>
> It's not initdb that's really complaining. The timezone files are not inputs
> to initdb. It's the postgres that initdb invokes that's complaining.
>> Postges will look for the share file in two places: the con
On 12/10/2010 11:19 AM, Tom Lane wrote:
> Robert Haas writes:
>> So in theory we could have a GUC under "file locations" to override
>> this, similarly to data_directory or hba_file or ident_file. But
>> since it's been like this for a really long time (I think), I wouldn't
>> be inclined to go m
Well, why are you configuring the prefix to be inside your build tree?
This is an odd thing to do. The prefix should be set to where you
expect to install the files, not where you're building them.
CONFIGURE = '--prefix=/home//build/Linux/qe_x86_64'
'--without-readline' '--without-zlib'
Still:
>>
>> In log2 I got the same errors as I mentioned earlier:
>> LOG: could not open directory "/home//.../share/timezone": No
>> such file or directory
>> ... ...
> Does it really have a pathname with three dots here?
>
> I'd have more confidence we knew what we were looking at if you sent
> the
On 12/09/2010 03:36 PM, BRUSSER Michael wrote:
> No, we do not use --with-system-tzdata option.
> I looked at the makefile and at the output of pg_config. We may need to do
> some cleanup there, but I did not pick any clues.
> The problem occurs on all our UNIX platforms.
> Is t
of pg_config if it helps, or try to run initdb with truss
or strace.
Thanks,
Michael.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, December 09, 2010 2:56 PM
To: BRUSSER Michael
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] initdb failure with
Initdb fails for me when host machine has no access to the Postgres build
location.
LOG: could not open directory .../install/share/timezone": No such file or
directory
LOG: could not open directory .../install/share/timezone": No such file or
directory
WARNING: could not open directory .../
We adding support for Solaris x86 and this pushes us to upgrade the from
the old-old version of Postgres we've been using for years.
(The requirement is to have the 64-bit exec and libs)
I looked at the release notes but could not figure out at which point
Postgres gave the option of building the
I need to repair the old version of Postgresql.
pg_dump does not work, I tried few other things but could not come up
with any workable scenario.
Any help will be greatly appreciated!
Thanks,
Michael.
cdb=# vacuum;
WARNING: Rel pg_proc: TID 31/20: OID IS INVALID. TUPGONE 0.
VACUUM
cd
If I can add my 2 cents as the end user, IMHO having the configuration
file
in the xml format is unnecessary and only makes it less user-friendly.
Thanks,
Michael.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Wednesday, June 04, 2008 4:5
I ran into a situation with the query that needs to fetch the last
record from the table.
The table schema wasn't really designed to support this, (no serial id,
or anything else I could use)
so SQL makes use of max(create_date) which has a resolution of 1 second
and thus allows for duplicate value
I wonder if there could be a potential problem with using this approach
-
checking on $USER == root.
Although it is a common practice, I think a superuser does not have to
be root.
If I'm right here, a better technique could be executing `id`.
Mike
-Original Message-
From: [EMAIL PROTE
s and stats collector process.
Do they actually use connections, decrementing what's available from
the max_connections value?
Thank you
-Original Message-
From: [EMAIL PROTECTED] On Behalf Of Bryan White
... ...
Brusser, Michael wrote:
> Is there a way to find a number of current c
Please disregard this duplicate
submission, my mistake.
Mike
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brusser, Michael
Sent: Friday, November 11, 2005
12:35 PM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] How to find a
number of connections
Is there a way to find a number of current connections on
Postgres 7.3.x ?
I looked at some system tables and views, but did not see
anything obvious.
Thank you,
Mike
Is there a way to find a number of current connections on Postgres 7.3.x
?
Thank you,
Mike
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Just occurred to me: perhaps we don't have a database corruption,
instead after replacement of the boot drive the locale on the host
changed from
en_US.ISO8859-1 to 'C'
Still I am not sure what to do. Is changing the locale back to
en_US.ISO8859-1
the right thing to do now?
Mike.
-Original M
Our customer reported a problem resulting from the hard drive failure.
Database server would not start, generating this message:
PANIC: The database cluster was initialized with LC_COLLATE
'en_US.ISO8859-1',
which is not recognized by setlocale().
It looks like you need to initdb.
They are
I can’t contribute with any
technical advice, but as a user I had to resort to using pg_resetxlog few times.
I wonder if it is possible to make it more
user-friendly. It was never clear to me whether it was sufficient to run it
without any arguments, and if not what these
arguments should
use
database. Still don’t understand what I’ve done.
Can somebody shed little light on what
actually happened?
Thanks,
Mike
From: Brusser, Michael
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June 16, 2005 8:28
PM
To: 'Pgsql-Hackers
(pgsql-hackers@postgresql.org)'
Subject
Title: MemoryContextAlloc: invalid request size
Our customer is reporting a database problem after they ran into a
disk quota/filesystem full situation.
This is Postgres 7.2.x on Solaris.
The database server starts without any obvious errors, but the app. Server
cannot establish connection
Title: fdatasync failed, I/O error
Our customer is running Postgresql v. 7.3.4 on Linux(Redhat 3.0 Ent.)
The application crashed and I am trying to understand what could have caused this kind of problems:
fdatasync of log file 0, segment 2 failed: input/output error
PGSTAT: Error clo
Title: RE: [HACKERS] Relation does not exist
> "Brusser, Michael" <[EMAIL PROTECTED]> writes:
> > Our customer reported a problem with Postgres v.7.3.2
> server on Solaris 8
> > I asked them to run a quick query and it looks like the database is
> >
Title: RE: [HACKERS] backend died
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 15, 2004 3:34 PM
> To: Brusser, Michael
> Cc: Pgsql-Hackers (E-mail)
> Subject: Re: [HACKERS] backend died
>
>
> "Bru
Title: RE: [HACKERS] backend died
> "Brusser, Michael" <[EMAIL PROTECTED]> writes:
> > Our customer running Postgres v. 7.3.2 reported a problem, occurring
> > couple times a week on three different servers, all on Solaris 9.
>
> > 2004-11-13 10:0
Title: backend died
Our customer running Postgres v. 7.3.2 reported a problem, occurring
couple times a week on three different servers, all on Solaris 9.
We enabled debugging in postgresql.conf, now it happened again;
here's the excerpt from the database log:
2004-11-13 10:01:06 [10456] DE
Title: Relation does not exist
Our customer reported a problem with Postgres v.7.3.2 server on Solaris 8
I asked them to run a quick query and it looks like the database is corrupted:
select count (1) from t_revisioncontrol
ERROR: Relation 17236 does not exist
What can I do next?
Thanks,
M
30 matches
Mail list logo
