I am getting the follow error:
analise3:/postgres/share/contrib/tsearch2 # make
Makefile:31: ../../src/Makefile.global: No such file or directory
Makefile:32: /contrib/contrib-global.mk: No such file or directory
make: *** No rule to make target `/contrib/contrib-global.mk'. Stop.
analise3:/postgr
Στις Παρασκευή 02 Φεβρουάριος 2007 14:05, ο/η Alexander B. έγραψε:
> I am getting the follow error:
>
> analise3:/postgres/share/contrib/tsearch2 # make
> Makefile:31: ../../src/Makefile.global: No such file or directory
> Makefile:32: /contrib/contrib-global.mk: No such file or directory
> make: *
yes, you need to just correct the build directory paths...
---
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 2/2/07, Achilleas Mantzios <[EMAIL PROTECTED]> wrote:
Στις Παρασκευή 02 Φεβρουάριος 2007 14:05, ο/η Alexander B. έγραψε:
> I am getting the follow error:
>
> analise3:/postgres/shar
Hi all,
I have two production server .One ia already live and the other is going
to live soon.
In the 1st server i have postgres 7.4.6 and having no problem
In the second server we have postgres (PostgreSQL) 7.4.15. Here i have made a
mistake. I have removed postgresql.
Am Freitag, 2. Februar 2007 13:05 schrieb Alexander B.:
> I am getting the follow error:
>
> analise3:/postgres/share/contrib/tsearch2 # make
> Makefile:31: ../../src/Makefile.global: No such file or directory
> Makefile:32: /contrib/contrib-global.mk: No such file or directory
> make: *** No rule
If you can tell the specific error on start/stop then someone might be able
to help you with this...
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 2/2/07, Manish Pillai <[EMAIL PROTECTED]> wrote:
Hi all,
I have two production server .One ia already live and the other is
going to
Hi,
I am getting only this much...
[EMAIL PROTECTED] init.d]# ./postgresql restart
Stopping postgresql service: [FAILED]
Starting postgresql service: [FAILED]
[EMAIL PROTECTED] init.d]#
How to enable log i
Instead of starting with the service, trying starting up with 'postmaster'
binary. It can be found in the database server 'bin' folder and that should
give a little more detail failure message.
To enable logging please go through --> "16.4.5. Error Reporting and
Logging" at
http://www.postgresql.
I have installed it using rpm..So "bin" folder is not available inside pgsql
:-(
Manish
Shoaib Mir <[EMAIL PROTECTED]> wrote:
Instead of starting with the service, trying starting up with 'postmaster'
binary. It can be found in the database server 'bin' folder and that should
You will always have a postmaster binary - do a "find / -name
postmaster" to find it.
If your secondary production server hasn't gone live yet, I'd seriously
consider starting it up on the 8.2 series.
Manish Pillai wrote:
I have installed it using rpm..So "bin" folder is not available
insi
Sorry for insist, but how can I add a new language, specially portuguese?
I could execute the file "tsearch2.sql", but I need to configure in my
language.
Thanks in advance.
Jeff Frost escreveu:
> BTW, this was for an RPM installed version of postgresql. As Shoab
> mentions in another mail,
below, you'll need to change every mention of english to portuguese and you'll
also need to find an ispell dictionary for portuguese. Also, this INSERT:
INSERT INTO pg_ts_cfg (ts_name , prs_name, locale ) values (
'default_english', 'default', 'en_US');
would need to match your locale, so rep
Le vendredi 2 février 2007 17:28, Alexander B. a écrit :
> Sorry for insist, but how can I add a new language, specially portuguese?
> I could execute the file "tsearch2.sql", but I need to configure in my
> language.
you should look at the tsearch2 site, there is a lot of info.
in few steps :
-
I am getting only this much...
[EMAIL PROTECTED] init.d]# ./postgresql restart
Stopping postgresql service: [FAILED]
Starting postgresql service: [FAILED]
[EMAIL PROTECTED] init.d]#
How to enable log in postgres...Pl
Shane Ambler wrote:
>
>>>I am getting only this much...
>>>
>>> [EMAIL PROTECTED] init.d]# ./postgresql restart
>>> Stopping postgresql service: [FAILED]
>>> Starting postgresql service: [FAILED]
>>> [EMAIL PROTECTED] init.d]#
>>>
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Shane Ambler wrote:
>> Your prob may be knowing where the log is. By default you will find it
>> in your data directory along with postgresql.conf and it will be called
>> serverlog
> likely /var/log/postgresql
> What linux is this?
There are enough
Thank you for the response. We are using Linux and I am able to identify
the offending . I was not sure if killing the process was an
acceptable and safe practice.
Thanks again!
Robert
Guido Barosio wrote:
Hmm, if you are a sysadmin you may want to get the process id for the
query, running so
I am attempting to get a handle on the corruption that caused
the following error:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: could not access status of
transaction 3183024
DETAIL: could not open file "pg_clog/0003": No such file or directory
pg_dump: The command was:
Hello,
I was wondering if there is some patch to apply for Postgres to handle the
changes in the daylight savings time for 2007.
Thanks
Abu
-
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
I wrote:
> I am attempting to get a handle on the corruption that caused
> the following error...
After a bit more digging I found a couple of old messages that helped -
http://archives.postgresql.org/pgsql-admin/2004-01/msg00258.php
The last tuple that is valid is (3, 123) and looking at record
See the FAQ on the web site.
---
Abu Mushayeed wrote:
> Hello,
>
> I was wondering if there is some patch to apply for Postgres to handle the
> changes in the daylight savings time for 2007.
>
> Thanks
> Abu
>
>
>
Robert Leftwich wrote:
> pg_dump: Error message from server: ERROR: could not access status
> of transaction 3183024
> DETAIL: could not open file "pg_clog/0003": No such file or
> directory
If your database system has already experienced on the order of 3183024
transactions, then you should wo
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Robert Leftwich wrote:
>> pg_dump: Error message from server: ERROR: could not access status
>> of transaction 3183024
>> DETAIL: could not open file "pg_clog/0003": No such file or
>> directory
> If your database system has already experienced on t
On Fri, 02 Feb 2007 21:21:47 -0500, "Tom Lane" <[EMAIL PROTECTED]> said:
>
> Yeah. What file names are actually present in $PGDATA/pg_clog/, and
> what does pg_controldata say about the current XID counter? We have
> seen some bugs where clog files get deleted before they're not needed
> anymor
"Robert Leftwich" <[EMAIL PROTECTED]> writes:
> On Fri, 02 Feb 2007 21:21:47 -0500, "Tom Lane" <[EMAIL PROTECTED]> said:
>> Also, can you show us the pg_filedump output for the page of
>> pg_description you think is trashed? I find "-i -f" options give
>> the most useful output usually.
> [ dump
On Fri, 02 Feb 2007 22:28:42 -0500, "Tom Lane" <[EMAIL PROTECTED]> said:
> This seems like it could indicate either a hardware or operating-system
> flake-out. Have you tried running hardware diagnostic tests on the
> machine?
>
A couple of weeks back when it had 'invalid page header' problems,
Hello All,
What strategies are people using for automated, script-based backup of
databases? There are a few I can think of:
1. Create a "db_backup" unix user and a "db_backup" pgsql user. Grant
READ access to all objects on all databases for the "db_backup" pgsql
user. Create a .pgpass
27 matches
Mail list logo
