Grant Finnemore <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Are you guys running with WAL enabled? If so, this is probably the
>> BufferSync issue that Hiroshi thought I broke a couple days ago.
>> Let me know...
> Yes, I am running WAL enabled.
OK, I put back the BufferSync call. Sorry '
> Are you guys running with WAL enabled? If so, this is probably the
> BufferSync issue that Hiroshi thought I broke a couple days ago.
> Let me know...
Yes, I too am running with WAL enabled.
- Thomas
Tom Lane wrote:
> Thomas Lockhart <[EMAIL PROTECTED]> writes:
> >> Is it just me?
>
> > I'm pretty sure I saw something similar on a newly initialized database.
>
> Are you guys running with WAL enabled? If so, this is probably the
> BufferSync issue that Hiroshi thought I broke a couple days ag
Thomas Lockhart <[EMAIL PROTECTED]> writes:
>> Is it just me?
> I'm pretty sure I saw something similar on a newly initialized database.
Are you guys running with WAL enabled? If so, this is probably the
BufferSync issue that Hiroshi thought I broke a couple days ago.
Let me know...
> Is it just me?
I'm pretty sure I saw something similar on a newly initialized database.
The sequence was:
initdb
postmaster -i -o -F
createdb
psql
(database "thomas" not found)
psql template1
\d
(see "thomas")
psql
(database "thomas" found just fine)
- Thomas
I did a CVS checkout today, and the following database creation fails.
In psql:-
You are now connected to database template1 as user postgres.
template1=# select version();
version
PostgreS
