Is there guide to compile PG?
- Original Message -
From: "Alvaro Herrera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Pavel Stehule" <[EMAIL PROTECTED]>; "Peter Eisentraut"
<[EMAIL PROTECTED]>; ; "Euler Taveira de Oliveira"
<[EMAIL PROTECTED]>
Sent: Sunday, August 24, 2008 8:06
[EMAIL PROTECTED] wrote:
Is there guide to compile PG?
http://www.postgresql.org/docs/8.3/interactive/install-win32.html
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
h
HI,
I have installed "Postgresql" but don't know the login password for
"sa".
please help me.
___
Jagu
Fidelity Business Services India.
Mobile: 9900540134
Direct : 40334528
Voip : 8-658-1596
Any comments or statements made in this email are not necessarily
Dear Sur!
My name is Peter Kovacs and I work at the National Szechenyi Library in
Hunagry.
The reason why im writing this letter is the follow:
We are using Potgresql to store our data. We have UTF-8, LATIN1 and
LATIN2 encoded databases.
I haven't got any problem with database encoding before,
Hello
PostgreSQL doesn't know username "sa". Same role is "postgres" in PostgreSQL.
What is your operation system?
regards
Pavel Stehule
p.s. it isn't bug, so mail to mailing list general -
http://www.postgresql.org/mailpref/pgsql-general
2008/8/25 Janardhanachari, Jagadeesha <[EMAIL PROTECT
[EMAIL PROTECTED] wrote:
The problem is that we need both UTF-8, LATIN1 and LATIN2 characters.
My question is: How could I create a database with NON-UTF-8 encoding.
Just use UTF-8. UTF-8 can represent all characters that are present in
LATIN1 and LATIN2.
You can still use LATIN1 or LATIN2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 25, 2008 at 12:29:14PM +0200, [EMAIL PROTECTED] wrote:
> Dear Sur!
>
> My name is Peter Kovacs and I work at the National Szechenyi Library in
> Hunagry.
> The reason why im writing this letter is the follow:
> We are using Potgresql to st
On Monday 25 August 2008 13:29:14 [EMAIL PROTECTED] wrote:
> ERROR: encoding LATIN2 does not match server's locale en_AU.UTF-8
> DETAIL: The server's LC_CTYPE setting requires encoding UTF8.
In 8.3, it no longer works to create databases of different or incompatible
encodings. You need to pick
2008/8/25 Janardhanachari, Jagadeesha <[EMAIL PROTECTED]>:
> What is the password for postgres ?
You filled it on win platforms, on unix platform this password isn't
filled. Try to login as system user postgres, then open local connect
to postgresql and then you can change password.
Pavel
>
>
> _
What is the password for postgres ?
___
Jagu
Fidelity Business Services India.
Mobile: 9900540134
Direct : 40334528
Voip : 8-658-1596
Any comments or statements made in this email are not necessarily those
of Fidelity Business Services India Pvt. Ltd. or an
In response to "Janardhanachari, Jagadeesha" <[EMAIL PROTECTED]>:
> What is the password for postgres ?
There is none. Please read:
http://www.postgresql.org/docs/8.3/static/client-authentication.html
Then take any further discussion on the matter to the pgsql-general@
mailing list.
--
Bill
[EMAIL PROTECTED] ("Janardhanachari, Jagadeesha") writes:
> What is the password for postgres ?
This isn't a bug, to be sure, and there isn't a password declared, by
default.
The account that is created, initially, by default, has *no* password,
which means you must connect via some means that d
The following bug has been logged online:
Bug reference: 4374
Logged by: Daniel Migowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Windows
Description:pg_restore does not restore public schema comment
Details:
Hello dear developers
The following bug has been logged online:
Bug reference: 4375
Logged by: Daniel Migowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Linux
Description:pg_dump documentation, -Z option
Details:
The option documentation misses the fact
"Daniel Migowski" <[EMAIL PROTECTED]> writes:
> Currently a schema dump (custom format, containing the public schema
> comment) can be restored, but the public schema version is not restored.
> I assume you check if a schema already exists and the skip the schema part.
That assumption is false, s
"Daniel Migowski" <[EMAIL PROTECTED]> writes:
> The option documentation misses the fact that you can produce gzipped output
> files with text format.
Huh, so you can. I wonder if anyone but Philip Warner ever knew that.
Docs updated ...
regards, tom lane
--
Sent via pg
This problem exists in 8.3.3:
=> create table foo(a int);
CREATE TABLE
=> create index foo_a_idx on foo(a);
CREATE INDEX
=> select max(a), generate_series(1,2) as g from foo order by g desc;
max | g
-+---
| 2
| 1
(2 rows)
=> explain select max(a), generate_series(1,2) as g from fo
Jeff Davis <[EMAIL PROTECTED]> writes:
> => select max(a), generate_series(1,2) as g from foo order by g desc;
> ERROR: set-valued function called in context that cannot accept a set
This strikes me as a pretty useless query, so the fact that it doesn't
work doesn't bother me. It's mostly accide
Tom Lane wrote:
> "Daniel Migowski" <[EMAIL PROTECTED]> writes:
>> Currently a schema dump (custom format, containing the public schema
>> comment) can be restored, but the public schema version is not restored.
>
>> I assume you check if a schema already exists and the skip the schema part.
>
>
Craig Ringer <[EMAIL PROTECTED]> writes:
> The issue actually appears to be that the comment on default schema like
> `public' isn't dumped in the first place.
Hmm ... there is a specific exclusion in _printTocEntry to suppress
dumping of either the CREATE SCHEMA command for "public" or its commen
On Mon, 2008-08-25 at 22:26 -0400, Tom Lane wrote:
> Jeff Davis <[EMAIL PROTECTED]> writes:
> > => select max(a), generate_series(1,2) as g from foo order by g desc;
> > ERROR: set-valued function called in context that cannot accept a set
>
> This strikes me as a pretty useless query, so the fa
Jeff Davis <[EMAIL PROTECTED]> writes:
> On Mon, 2008-08-25 at 22:26 -0400, Tom Lane wrote:
>> ... It's mostly accidental that there are any
>> variants that do work, I think. Why would you want a SRF in a sort key?
> The following line was added to the regression tests:
> aggregates.sql:226:
>
22 matches
Mail list logo
