Allan Tong <[EMAIL PROTECTED]> writes:
> I'm not sure if this is the right list to send this, but any help
> would be appreciated. We recently encountered a problem running
> postgres where, after a vacuum, all the data in one of our tables
> was gone. Now, I guess technically we don't know for s
Denis N. Stepanov wrote:
> snprintf()/vsnprintf() functions are not ANSI-compliant
Yes, they are.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
On Thu, 8 Jan 2004, Tom Lane wrote:
TL> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
TL> > Some OSes lack proper snprintf()/vsnprintf() fuctions so PostgreSQL includes
TL> > its own version (src/port/snprintf.c) during building. Unfortunately, this
TL> > version of snprintf() is not reentran
I'm not sure if this is the right list to send this, but any help
would be appreciated. We recently encountered a problem running
postgres where, after a vacuum, all the data in one of our tables
was gone. Now, I guess technically we don't know for sure if it
was indeed vacuum that caused the da
