-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
| it takes a while (i dont know how much) for the .backup file to get
| archived and appear in the wal archive area. thats why i prefer to
| use the wal log filename (0001000A0068) instead of
| something lik
On 4/3/06, Brendan Duddridge <[EMAIL PROTECTED]> wrote:
> Whenever you get a finalized script including all the enhancements
> you've been talking about,
> I would really love to have a copy as I'm sure lots of people here
> would. I think this is
> something that should be included in the standard
Whenever you get a finalized script including all the enhancements
you've been talking about,
I would really love to have a copy as I'm sure lots of people here
would. I think this is
something that should be included in the standard distribution.
Can I make a couple of suggestions?
1. Inclu
Please could someone help me with my questions below?
On 3/25/06, adey <[EMAIL PROTECTED]> wrote:
Two questions in this regard please?
1) Is tuple theory not the root of this problem
2) Vacuum does much the same as a traditional database reorg, and online reorgs are a reality now
1) If I unders
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> The handwriting on the wall says that autovac will soon be on by
>> default, and perhaps become not-disablable some day after that
>> (like the second or third time we hear from someone who's lost
>> their data to XID wraparound after
Tom Lane wrote:
> The handwriting on the wall says that autovac will soon be on by
> default, and perhaps become not-disablable some day after that
> (like the second or third time we hear from someone who's lost
> their data to XID wraparound after disabling it).
I don't think we will see much p
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Unfortunately, the SQL committee did tremendous damage to that
>> argument by changing the definitions of some of those views in
>> SQL2003 :-(
> The only changes to existing views were one renamed column and two or
> three cases w
It looks like moving to FreeBSD 6.x for some of our servers is biting me
in the butt ... they "broke" something with semaphores that used to work
with 4.x, so that you can't run two postmasters on port 5432 within two
seperate jails ... :(
On Sun, 2 Apr 2006, Marc G. Fournier wrote:
What
Tom Lane wrote:
> Unfortunately, the SQL committee did tremendous damage to that
> argument by changing the definitions of some of those views in
> SQL2003 :-(
The only changes to existing views were one renamed column and two or
three cases with relaxed permission checks so that more objects are
What would cause the following?
# psql -U pgsql -l
psql: FATAL: semctl(327686, 3, SETVAL, 0) failed: Invalid argument
The server is FreeBSD 6.1-PRERELEASE ... there are two jails running on it
... both jails are running PostgreSQL 7.4 ... I have the kernel built with
enough semaphores:
opt
Rajesh Kumar Mallah wrote:
> Another area i was thinking to improve this script was to
> make it dig out all the tablespace folders to be archived by looking
> into PGDATADIR/pg_tblspc . This shall make the script more generic.
>
> pg_tblspc as contents like below:
>
> $ ls -l
> total 0
> lrwxr
"Rajesh Kumar Mallah" <[EMAIL PROTECTED]> writes:
> information_schema is the standard which are more likely to behave
> the same in all versions of pgsql becoz they are(currently) views on
> the sys catalogs.
Unfortunately, the SQL committee did tremendous damage to that argument
by changing t
On 4/2/06, Grega Bremec <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Rajesh Kumar Mallah wrote:
> |
> | Instead of taking a round about method i am using the content of the
> | file, (This was also suggested by Andy at somepoint)
>
> After reading the docs a
Thanks Rajesh,
That's always a risk anyway with anything - hence where upgrade testing
comes in ;-)
I'll probably go this way if I do indeed have this need still - it was only
a preliminary thought process, I just thought I'd ask the question.
Thanks
Andy
-Original Message-
From: [EMAIL
On 4/2/06, Andy Shellam <[EMAIL PROTECTED]> wrote:
> > After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED]
> ("Andy Shellam") belched out:
> >> Is there an SQL command supported by Postgres to return a list of tables
> in a database?
>
> Sorry, did I say something wrong? I thought it was a
> After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED]
("Andy Shellam") belched out:
>> Is there an SQL command supported by Postgres to return a list of tables
in a database?
Sorry, did I say something wrong? I thought it was a perfectly valid
question actually. The application in mind is
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rajesh Kumar Mallah wrote:
|
| Instead of taking a round about method i am using the content of the
| file, (This was also suggested by Andy at somepoint)
After reading the docs again, that's what I would do as well, indeed. :)
| lately i feel
On 4/2/06, Christopher Browne <[EMAIL PROTECTED]> wrote:
After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] ("Andy Shellam") belched out:> Is there an SQL command supported by Postgres to return a list of tables in a database?
Yes, it's called SELECT.There is a standard schema called INFOR
After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] ("Andy Shellam")
belched out:
> Is there an SQL command supported by Postgres to return a list of tables in a
> database?
Yes, it's called SELECT.
There is a standard schema called INFORMATION_SCHEMA, which contains a
variety of releva
Hi Grega,
That's perfect thanks. I needed the SQL as it will be running in a web
application, and I need to use the resulting list for processing within the
application.
Many thanks
Andy
-Original Message-
From: Grega Bremec [mailto:[EMAIL PROTECTED]
Sent: Sunday, 02 April, 2006 10:34
On Sun, 2 Apr 2006, Grega Bremec wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Andy Shellam wrote:
| Hi,
|
| Is there an SQL command supported by Postgres to return a list of
| tables in a database?
|
| For example on mySQL, you can connect to a database and issue the
| command SHOW
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Andy Shellam wrote:
| Hi,
|
| Is there an SQL command supported by Postgres to return a list of
| tables in a database?
|
| For example on mySQL, you can connect to a database and issue the
| command SHOW TABLES to bring back a list of tables in
Hi,
Is there an SQL
command supported by Postgres to return a list of tables in a
database?
For example on
mySQL, you can connect to a database and issue the command SHOW TABLES to bring
back a list of tables in that database.
In PG this throws
the error "unknown configuration parameter
23 matches
Mail list logo
